John Plocher wrote: > Right. The "API" I was asking about is the server-side URL that > XMLHttpRequest > talks to - I don't have access to the server that the database is > running on, > so I can't write the code under that URL...
Correct. > i.e., the user connects to arc.opensolaris, gets my page, and on my page > there > is javascript that needs to get the list of cats/projects... > > The browser can't cross connect to auth.opensolaris because of the security > protections in the browser, so it needs to contact arc.opensolaris for > the lists. Correct. > So, the Q is how can I (on arc.opensolaris) get access to the data? If the > URL is a stable API, then I can have my server grab the data by treating > it as > a web service.... > > I'm assuming from this email that this will be your XMLRPC interface, > but that > it isn't there yet? Correct. There will be a number of XMLRPC services which will allow authenticated applications to query data about the opensolaris community. And correct, it isn't available yet. I'm writing the admin webapp first, to allow the database to be managed. Follow-on tasks include: Implementing authentication on the admin webapp. Writing a user registration/update webapp. Writing user cookie handling code. Writing the XMLRPC server. Writing at least one XMLRPC client library. Testing all of the above. Migrating all the data from the existing database. Migrating all the existing applications (OSO webapp, SCM console, voting system, code review system etc) to use the new framework. > Clear as mud? Perfectly ;-) -- Alan Burlison -- _______________________________________________ website-discuss mailing list [email protected]
