Community
Participate
Working Groups
We should run the User Service as a Plugin.
(In reply to comment #0) > We should run the User Service as a Plugin. I would like to know why - not everything should be a plugin because we can make it a plugin.
The future idea is that we will make FileService a plugin. We need to authenticate on orion to get to file service not to get to the client, so the idea is that each FileService plugin should be provided with matching UserService plugin.
So far the most important data needed by File Service are authorization rules, which will be available via User Service. We need to host both services on the same site then... at least so far. If you want access User Service from your Orion client later, the only way is to do it via the Plug-ins mechanism.
See also Bug 337104.
(In reply to comment #4) > See also Bug 337104. Sorry. I meant Bug 336188.
Created attachment 189118 [details] mylyn/context/zip I committed the first version. Only user profile uses it now. I used event notifications as an alternative to callback functions. Unfortunatly I didn't manage to solve the problem of authentication (and other error handling done by handleAuthenticationError), so profile works only when you are logged in.
Done