Rob,

Although ZOOM doesn't define what goes over the wire, it does provide a
abstract Object Oriented model from which a specific implemetation
(Java, C++ etc.) can be derived.

GRIDServices are really a Object Oriented approach of doing WebServices.
Essentially a GRIDService is a WebService which is created on demand for
a particular user and can then be destroyed on request.  

As such a GRIDService binding for ZOOM is fairly easy to construct (and
makes more sense than a WebService binding). I did suggest this to Mike
sometime last year (with little interest...)

Matthew

> -----Original Message-----
> From: Z39.50 Next-Generation Initiative [mailto:[log in to unmask]] 
> On Behalf Of Robert Sanderson
> Sent: Sunday, September 28, 2003 12:16 AM
> To: [log in to unmask]
> Subject: Re: Meeting this week
> 
> > > Zoom is an excellent abstraction for object oriented IR, 
> but doesn't
> > > define a protocol itself ... it's just an OO interface to 
> Z39.50 (and more
> > > recently to SRW in some implementations)
> 
> > I don't quite understand why this is a problem.  Are you saying that
> > Zoom does not imply any sort of protocol behind it?  In a 
> sense all we
> 
> Right.  It could work via FTP, LDAP, Z39.50, SRW, or anything 
> else.  All
> it defines is a standard API to use for OOP IR.  It was defined with
> reference to Z39.50, but is also easily useful with SRW.  
> What it doesn't
> do is say anything about what goes over the wire, as that's 
> is defined by
> the Z39.50 protocol. Zoom is just an abstract API. Mike would 
> be the best
> person to discuss this though.
> 
> Rob
> 
> --
>       ,'/:.          Dr Robert Sanderson ([log in to unmask])
>     ,'-/::::.        http://www.o-r-g.org/~azaroth/
>   ,'--/::(@)::.      Special Collections and Archives, extension 3142
> ,'---/::::::::::.    Nebmedes:  telnet: nebmedes.o-r-g.org 7777
> ____/:::::::::::::.                WWW: 
> http://nebmedes.o-r-g.org:8000/
> I L L U M I N A T I
> 
>