[Pipet Devel] PAOS and the Work Flow System

[Humberto Ortiz Zuazaga]

bizzaro at bc.edu said:
> There are more updated terms for what Carlos says below:

> Gnome clients == Benchtop + FigBuilder

Carlos seems to mean any GUI locus.

> Tool Manager == The part of a
> viewer (or maybe a separate process) that communicates via the WFS. 

No, I think Tool Manager == analytical locus.

Carlos said:
> I totally agree that Paos shouldn't shuffle around real data. I see
> the role of Paos as a coordination tool but not as a database
> management system.

If PAOS won't shuffle data around, we'll need another mechanism for getting 
data into an analytical locus.  It will have to be able to contact remote loci:

I fire up my seqence editor, type in a few bases from my still wet autorad, 
and click on the blast button.

The sequence data will have to be transfered to the remote blast locus.

The python XML topic guide at:

http://www.python.org/topics/xml/xml.html

lists two proposals for an XML over HTTP RPC mechanism, this or something 
similar can be used as loci's "transfer" mechanism (in the sense transfer is 
used in the glossary). These particular proposals seem a little too low level 
(they define a XML for bytes and integers etc), but the basic idea of using 
XML to transfer data and specify a remote procedure call syntax seems like 
what we need.

-- 
Humberto Ortiz Zuazaga
Bioinformatics Specialist
Institute of Neurobiology
hortiz at neurobio.upr.clu.edu