I'm busy building a .NET WCF framework for my company which will allow us to quickly and easily implement community type websites moving forward. The framework currently caters for things like Blogging, Forums and commenting on them etc.
I wanted to now implement Membership into the framework, and read up about ASP.NET Application Services, which seemed really easy to configure and implement, and I've used the ASP.NET membership stuff in websites I've developed before and really like it.
So far I've successfuly implemented the Authentication Service, Profile Service and Role Service successfuly in the Web Project that is hosting my other WCF services for our framework. The idea now is to build another website that uses these webservice methods to Login, GetPropertiesForCurrentUser, GetRolesForCurrentUser etc. Therefore I've created a new Website and added a service reference to my framework's WCF services. I can see that I'm able to call a Login method etc, but what I want to know is if this is how application Services was intended to be used, or if its only intent was for it to be used in Client Applications, as Ive started to notice some difficulties around Cookies etc.