[ome-devel] updates to back-end, ome-java, and shoola

Jason Swedlow jason at lifesci.dundee.ac.uk
Thu Apr 28 12:49:08 BST 2005


Hi All-

This sounds really great.  Very nice work.  This hopefully gets the 
major forms of these problems solved for now, and allows us some time 
to explore alternatives that require more work.

As far as a merge goes, we've discussed this a bit.  Here is a proposal.

1) We tag current HEAD (i.e., pre-merge) as OME2_4_1 (or whatever, just 
something that let's us access this).

2) We go ahead with merge.

3) We take that new code and put it on one of our dev servers here and 
test it with multiple users, big data etc.  Fix bugs, blah blah.

We can then decide when to release.

OK?

Jason

Begin forwarded message:

> From: Harry Hochheiser <hsh at nih.gov>
> Date: 27 April 2005 15:27:39 BST
> To: ome-devel <ome-devel at lists.openmicroscopy.org.uk>
> Subject: [ome-devel] updates to back-end, ome-java, and shoola
>
>
> As the changes I've made to various pieces of the xml-rpc server, 
> ome-java , and shoola are basically complete and solid, I'd like to 
> try to merge them back into head. A summary of what's been done:
>
> 1) Server: Several changes have been made to the back-end, in hopes of 
> improving XML-RPC performance. These changes include:
>
> 	- A modified Soap::Lite serializer (OME/Remote/SerializerXMLRPC.pm), 
> which allows for the possibility of passing 	appropriately blessed 
> objects through without trying to serialize them. This is necessary 
> for the support of facades that 	construct their own XML-RPC on the 
> fly: such facades can simply bless the results and have them pass 
> through the
> 	serializer untouched.
>
> 	- An alternative XML-RPC handler. OME/Remote/RPC2.pm and 
> OME/Remote/XMLRPC.pm are modified versions of
> 	a much simpler xml-rpc package. I found that this gave better 
> performance for our requests, so I added this as an option. 	This 
> version also includes the ability to create hand-crafted XMLRPC 
> responses and have them pass through untouched.
>
> 	- A revised httpd.omeds-dev.conf file, making /shoola the default 
> location using the new XML-RPC handler, and     	/shoolasoap   point 
> to the original handler based on Soap::Lite. These two alternatives 
> play together quite nicely with	 minimal changes to Facade.pm
> 	
> 	- Special-purpose facades for retrieving data useful for the 
> Chainbuilder - ChainRetrievalFacade and     	ModuleRetrievalFacade.  
> These facades retrieve data using something close to a "one 
> query/table" approach, and then 	stitch the results together, directly 
> into XMLPRC.
>
> 	- Revision of ome-java code generation components, as described below.
>
> 2) OME-JAVA:
>
> 	- Support for the new facades via new managers.
>
> 	- Revision to lazy instantiation. Previously, any data returned to 
> XML-RPC would have all components completely 	instantiated with DTO 
> objects upon return. This would require traversing a hash of hashes 
> and instantiating each object 	as it was seen. I modified this code to 
> make this instantiation "lazy": top-level objects are instantiated 
> upon return, but any 	sub objects will only be instantiated upon 
> requests, with results cached as need be.  Doing this required 
> changing the dto 	code,  which meant changing the code generation 
> facilities in the main ome distirubtion.
>  	
>
> 	- Lazy checking for null strings. Instead of traversing the entire 
> DTO & replacing the null marker (special string returned by 	xml-rpc 
> to indicate a null string) with an actual null string, ome-java now 
> does this on the retrieval of the value.
>
> 	- A few miscellaneous test scripts.
>
> 3) Shoola
>
> 	- Some new code in OMEDSGateway and revisions to DMSADapter to expose 
> the new facilties in ome-java.
>
> I've tested all of these things via OME-SRV-TESTS, my test programs in 
> OME-JAVA, and informal testing via the Shoola interface.
>
>
> As these changes are pretty broad, I'd obviously like to merge them 
> with care. My proposal is to tag everything and then merge the changes 
> in to ome, OME-JAVA,  Shoola, and OME-SRV-TESTS.
>
> Questions/comments/feedback appreciated. I'd be glad to provide more 
> detail about the changes that I've made. Advice on how best to do do 
> the merge would be most helpful.
>
> -harry
>
> _______________________________________________
> ome-devel mailing list
> ome-devel at lists.openmicroscopy.org.uk
> http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel
>

NOTE NEW EMAIL ADDRESS: jason at lifesci.dundee.ac.uk
**************************
MSI/WTB Complex
The University of Dundee
Dow Street
Dundee  DD1 5EH
United Kingdom

phone (01382) 345819
Intl phone:  44 1382 345819
FAX   (01382) 348072
email: jason at lifesci.dundee.ac.uk

Lab Page: http://www.dundee.ac.uk/lifesciences/swedlow/
Open Microscopy Environment: http://www.openmicroscopy.org
**************************
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 5077 bytes
Desc: not available
Url : http://lists.openmicroscopy.org.uk/pipermail/ome-devel/attachments/20050428/f11a57e4/attachment.bin


More information about the ome-devel mailing list