|Re: [ecf-dev] RemoteService + Context|
On 10/27/2010 10:19 AM, Radostin Surilov wrote:
Hi Franky, hi Scott,
One thing to make clear: although there is no problem with using the ecf generic provider, the code in org.eclipse.ecf.provider.remoteservice bundle does *not* depend upon the ECF generic provider (yes, I know the package name org.eclipse.ecf.provider.remoteservice.generic makes it sound like that, but that's an unfortunate package name that I now cannot change without breaking existing API).
Rather, the org.eclipse.ecf.provider.remoteservice depends upon the shared object API...and this API is currently implemented by several providers: xmpp, jms, javagroups providers. This allows *all* of these to reuse the RegistrySharedObject (and the Request/Response classes).
I don't see any problems with this. I think the discussion about more elegant solution can be had around whether or not some new API should be added to either ECF remoteservices...or the RegistrySharedObject...but I think given your use case what you've done makes sense. And I assume it's working for you.
If you are willing, maybe you could share the Request/Response subclasses and the RegistrySharedObect subclasses, and that would allow Franky and all of us to see if there are things that could be generalized to meet several authentication use cases with future API additions/changes.