John Plocher wrote: > I'm assuming you have a demo client "stack" that can be used as > a working example for us to build upon. As I don't know the > best practices (etc) that y'all have set up on the other *.os.o > infrastructure sites, and I have no interest in reinventing it > foible by foible myself, I'm looking for a "clone this" example.
There is a test Java client available from the repository on auth.opensolaris.org which makes calls to the XMLRPC API. There are no other language bindings at present. The documentation for the small portion of the XMLRPC API which exists so far can be found at http://auth.opensolaris.org/auth/xmlrpcapi/ I'm working on adding new XMLRPC functions at the moment, my development workspace has additional calls and I'm busy adding more. None of this has been rolled out to oso because it is still under development. We need to get the Auth application finished and all the data migrated from the current database before we can offer a 'live' service, although I'd be delighted if people wanted to kick the tyres of the test system which is currently running on auth.opensolaris.org. I'd need to provide some documentation (other than the documentation that is in the source) to make that easier for people. Once we have the Auth app finished we have to retrofit the new Auth mechanisms into all the existing oso applications, whilst keeping the site 'live'. The details of how this is going to be done are fairly involved and won't make much sense without a fairly deep background knowledge of the current site infrastructure, so I'm not going to go into any further detail other than to say 'It's complicated'. > It may be that the easy answer is to copy/paste a 10 line perl, > php or python script and go from there. That doesn't exist at present. You can get a flavour of how the Java API works from here: http://auth.opensolaris.org/svn/showfile.svn?path=%2ftrunk%2fAuthClient%2fsrc%2fauthclient%2fMain.java&revision=HEAD&name=auth > I also want us to be able to host a hg repo on src.os.o so that > the interested parties can use to develop this stuff - and that > can be connected to the web stack on arc.os.o such that putbacks > to the repo can be propagated to the running/deployed site for > demo/testing/use. As I again have no desire to be the sysadmin > or webmaster that has to invent all the plumbing from scratch, > I'm looking for reusable clue. I think the correct place would be a project on oso, with an associated repository - all the mechanisms for that are already in place. Are you suggesting that stuff that gets committed to such a repo automatically gets deployed on arc.os.o? That seems kinda risky... I'm not quite sure what you mean by 'plumbing' as I'm not entirely sure of what you are trying to achieve. -- Alan Burlison --
