LISTSERV mailing list manager LISTSERV 16.0

Help for ZNG Archives


ZNG Archives

ZNG Archives


[email protected]


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

ZNG Home

ZNG Home

ZNG  December 2004

ZNG December 2004

Subject:

Unrequested Extensions again (Was BL SRU)

From:

Dr Robert Sanderson <[log in to unmask]>

Reply-To:

Z39.50 Next-Generation Initiative

Date:

Fri, 31 Dec 2004 13:03:30 +0000

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (61 lines)

In summary:

Unless the client knows how to process this information, it's useless and
wasting everyone's bandwidth and processing time.

If the client does know how to process this information, it can also be
able to request it.


> I think a server may have the following reasons for including
> extraResponseData that are independent of what the client requests :
> To identify ownership of the data/response.
> To show where the response came from.
> To provide additional data which will help process the response.

All of which can only be processed by a client which knows what the data
means.  If the client can process it, it can request it.

> To provide diagnostic information in the response, not necessarily for the
> purposes of the client.

If you need over-the-wire debugging facilities, then the client can
request them.  But including all of the information in every response is
just simply bad manners and just plain wrong.


> The client can ignore data it does not require. Why should it "break" the
> processing in the client, unless the client is not conforming to the schema

Because this information comes in the form of arbitrary elements.
A SOAP toolkit that can't handle this will likely just refuse to process
the response, and hence will be unable to use the service at all.

For XSLT based processing, unless there is an XSLT rule to process the
information, it'll end up being dumped into the output stream, potentially
breaking the application.


> While the additional parameter is one way of defining the additional data
> included in the response (http headers might be an alternative) it requires
> the client to know this parameter and that it has a means of setting this
> parameter, either automatic or user driven.

Yes. And, as above, if the client can process the information, it can
request it.  The code required to request it is probably one line.  The
code required to process it once requested is liable to be many more than
that.

HTTP headers might be an alternative, but they're not the way SRW/U uses.
Notably as SOAP doesn't specify HTTP as a required transport protocol, and
there's no reason why SRW should have to be transported via HTTP.

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

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

July 2017
October 2016
July 2016
August 2014
February 2014
December 2013
November 2013
October 2013
February 2013
January 2013
October 2012
August 2012
April 2012
January 2012
October 2011
May 2011
April 2011
November 2010
October 2010
September 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
October 2009
September 2009
August 2009
July 2009
May 2009
April 2009
March 2009
February 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager