> <serverInfo protocol="SRU" version="1.1" transport="http">
> <host>gondolin.hist.liv.ac.uk</host>
> <port>210</port>
> <database>IR-Explain---1</database>
> </serverInfo>
> Since serverInfo is non-repeatable (if my understanding of DTD is
> up-to-date) there is no way to supply more than one
> host/port/protocol/transport combo..
Correct. If you need to provide more than one, then you'll have separate
endpoints. (Note the existence of SRWU for the protocol attribute to say
that you support SRW and SRU at the same endpoint)
> Hmm, that's just a simple client-side fix. But the client should be able
> to find out whether the server actually supports it..
> I propose to extend ZeeRex:
> - make serverInfo repeatable
Ergh, no. If you listen to multiple ports, then the explain information
for that port should be available at that port, via the explain operation.
There's the links section for linking to other interfaces.
> - add an attribute @method to <serverInfo>
I'm not against this when @protocol="SRU" or "SRWU"
> Question: does protocol="SRW" need extra attributes like RPC or
> doc/literal ?? I don't know enough about SOAP for that..
Nope, that's specified in the one true WSDL for the protocol.
Rob
,'/:. Dr Robert Sanderson ([log in to unmask])
,'-/::::. http://www.o-r-g.org/~azaroth/
,'--/::(@)::. Dept. of Computer Science, Room 805
,'---/::::::::::. University of Liverpool
____/:::::::::::::. L5R Shop: http://www.cardsnotwords.com/
I L L U M I N A T I
