> If you really want to use the simplest ServiceClient API (where we auto > create a dumb service underneath) then you can still do that .. pass > null as the 2nd arg. So we already have the capability you're looking > for.
Oops, sorry I should have read the code. I do not notice I can pass null > I'm still not convinced your scenario is very common: the user is > advanced enough to create their own repo etc., but only wants to use the > dumb anonymous service? Doesn't compute for me. But hey, its > supported :). At the client side service hardly matter! one can engage the modules at the client API. But two repositories will be very common if specs like RM/Secure conversation/Trust ever come to day to day use. On the other hand if the client is ever serious about the performance he better use one repository. One do not need to load complete repository per each invocation (do we recycle same repository for multiple instance of Service Client? ) Sorry for messing it up, I should have notice I can pass null as a argument :) Thanks very much Srinath
