[Pipet Devel] Another XML proposal - Part 1.

Humberto Ortiz Zuazaga hortiz at neurobio.upr.clu.edu
Tue Apr 6 09:45:20 EDT 1999


> (I think your clock is set to last Wedneday.)

Err, no, our 56K line was down from Wed till Monday.  Good Thursday and Good 
Friday are national holidays in Puerto Rico.

> 
> Humberto Ortiz Zuazaga wrote:
> 
> > Yes, this is good.  Installing a display locus (from wherever, more on this
> > later) should register the locus as able to display a certain set of DTDs, 
> 
> Yes.  Although it may be best that loci do not register themselves, that they
> are only registered when the app broker requests registration.

Well, we've got a couple of different app brokers, but I think the local app 
broker should be notified when local loci are installed.  It's cheaper and 
simpler.  Remote loci can be queried on demand or polled, but it may be 
simpler as well to just broadcast a notice of availability when the locus is 
turned on. This notification can then be propagated among interested app 
brokers.

> > The trick then is how the app broker finds out about loci at remote sites.
> 
> Of course you mean command-line analysis loci (which can return a GUI).  Really,
> the same way it finds out about local loci.  PAOS should make the connections
> seamless, so Loci "thinks" all loci are local (with the exception of security
> issues).

Here's where I get lost.  I haven't read the PAOS documentation (shame on me), 
can someone summarize what PAOS can do in the context of App Brokers locating 
loci?

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




More information about the Pipet-Devel mailing list