The code to handle SOAP is trivial. In my opinion, more trivial than the
code to live without SOAP. I think the code I mailed out demonstrates this.
The SOAP RPC code required no knowlege of SOAP. I just wrote the code to
handle the request and the rest of the infrastructure was provided by my
toolkit. The vast majority of the code was in handling the non-SOAP based
URL request and forming the XML response record.
> -----Original Message-----
> From: Theo van Veen [mailto:[log in to unmask]]
> Sent: Wednesday, October 31, 2001 4:35 AM
> To: [log in to unmask]
> Subject: Betr.: FW: Re: are there already zng-targets
> We have an ZNG-server without SOAP running in a very short
> time. It was also no problem to write an in a very short time
> a HTML-page serving as a ZNG-gateway. The root element of
> our response is searchRetrieveResponse.
> The use of SOAP makes things more complex and it will
> certainly result in a higher implementation barrier. Maybe it
> is a stupid question but I am wondering now what is the added
> value of SOAP in this standard. I know it makes sense in case
> on none-ascii input.
> Secondly to keep the implementation barrier low, isn't it a
> good idea to respond only with a SOAP envelop if the request
> was also embedded in SOAP?
> The power of simplicity can be of great value to spread the
> use if ZNG.
> >>> [log in to unmask] 30-10-01 21:54 >>>
> FYI - this is still flakey in places and only handles the URL form at
> present. Currently returns records in Yanks (Redsox ot whatever)
> > -----Original Message-----
> > From: Antony Corfield
> > Sent: 30 October 2001 17:05
> > Our ZNGServlet can be found at the address below, using the type of
> > shown. Attribute mapping can be specified as bib1.author or
> > etc. Default is bib1.
> Antony Corfield Java Developer JAFER Project
> mailto[[log in to unmask]] Libraries Automation
> tel: +44 (01865) 284454 99 Banbury Rd
> fax: +44 (01865) 278275 Oxford OX2 6JX