"J.W. Bizzaro" wrote: > > Talks with Gary (for those who don't know, Gary and I met in person over a > week's time to hash out some design issues) led me to start calling Loci a > 'connectivity broker'. This means that Loci will be agnostic to the > communications protocol used by the back-end program. CORBA, HTTP, COM, UNIX > pipes, XML_RPC, etc. can all be supported if the support is 'plugged in' to > Loci. Why? > > BECAUSE MANY, MANY PROGRAMS HAVE THEIR COMMUNICATIONS > PROTOCOL BUILT-IN (e.g, Apache), AND FORCING THESE PROGRAMS > TO CHANGE PROTOCOLS WOULD BE A MESS AND JUST PLAIN WRONG(TM). > AND LOCI WOULD OTHERWISE BECOME LIMITED TO WORKING ONLY WITH > PROGRAMS THAT ARE COMPATIBLE WITH...CORBA, OR WHATEVER. Word. > > But, you're right that the first programs to make work under Loci should be > bioinformatics apps. And it would be nice if we could the the corba connectivity up and running right away. There's a lot of excitement with bioperl, biopython, ebi, etc etc on corba connectivity, so we could possibly recruit some help from these groups to get it up and running. Regards, g. -- Gary Van Domselaar gary at bioinformatics.org http://www.bioinformatics.org/~gary ---------------------------------------------------- bioinformatics.org: The Open Lab http://www.bioinformatics.org/