[chimera-dev] publish collaboratory idl files?
gregc at cgl.ucsf.edu
Fri Feb 3 11:20:48 PST 2006
On Wed, 1 Feb 2006, David E. Konerding wrote:
> Greg Couch wrote:
>> So what is the real issue? Do you want a continuous remote interface to
>> chimera? Is the overhead of the --send option a problem? Please tell us.
>> There are probably alternative solutions that are better.
> Hi Greg,
> Yeah, the continuous remote interface, with explicit ability to access
> molecular objects, along with notifications of changes to the objects,
> are what I want.
> We have plenty of experience with building web services; I would suggest the
> following alternative (the problem being mainly a matter of increased
> developer time compared to the CORBA approach): convert the CORBA IDL files
> to XML schema, use our ZSI package to generate
> the Python bindings, then build a 'collaboratory hub grid service' (I say
> grid service instead of web service since the basic web services
> specs left out notification and messaging, but . All the concepts in CORBA
> map more or less directly to web services,
> so conversion of the collaboratory implementation code would be pretty
So first of all, we would be happy to provide you with the CORBA IDL files
so you could write the code yourself :-). However, our current preferred
method would be for you to write an extension that supported the subset of
the chimera functionality that your application needs. You, as the
original collaboratory author, are uniquely qualified to do so. A UCSF
maintained solution would be better, but we're not ready to standardize
that part of chimera yet.
More information about the Chimera-dev