On Tue, Aug 26, 2014 at 6:07 PM, Danny Ayers <[email protected]> wrote:
> On 26 August 2014 11:08, Reto Gmür <[email protected]> wrote: > > > That should be an easy one.... > > > > Should be :) Just tried doing pre-emptive auth, according to: > > > http://hc.apache.org/httpcomponents-client-ga/tutorial/html/authentication.html > > but I'm still getting the 401 challenge, so I guess I'll try doing the > regular two-step auth. > > > > > But if you're application is running in OSGi you definitively shouldn't > do > > this. You don't want to have to configure your app to store the password > of > > the instance it is running on (and need to reconfigure it, wehn the > > password is changed). > > > Hmm, I see your point, but what if an account is set up, reserved for the > app, on install, wouldn't that be feasible? > Well you app could set up an account for its own access. It would still need to store the (random) password it set for its user on disk, which is not ideal but certainly better than requiring the user to provide the password. > > I would prefer keeping the comms as much as possible still over HTTP rather > than OSGi, more potential for distributed systems. > Interesting. Did you have a look at DOSGi? Currently what I've been using it to separate the triple store from the OSGi instance by using the clerezza virtuoso binding. You are thinking of each bundle having a different Triple store configured as Sparql HTTP endpoind? This might be a usecase for having TcManager provided by a service factory, this way it would be possible to have another instance of TcManager depending on the bundle requesting it. This would be transparent for the bundles, because I think it really shouldn't be necessary for service implementors to care about the backend. On the other hand there should be a unified interface for the administrator to manage this distributed system. Cheers, Reto > > Cheers, > Danny. >
