LISTSERV mailing list manager LISTSERV 16.0

Help for ZNG Archives


ZNG Archives

ZNG Archives


ZNG@C4VLPLISTSERV01.LOC.GOV


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  April 2010

ZNG April 2010

Subject:

Re: Add "reliability" index to CQL's "zeerex" context set

From:

"Edward C. Zimmermann" <[log in to unmask]>

Reply-To:

SRU (Search and Retrieve Via URL) Implementors

Date:

Thu, 15 Apr 2010 14:22:03 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (105 lines)

The question is less that one might want to relate something but the semantics
of what one is relating unless its purely private--- and then its not trying
to relate to anyone but only itself. 

What does a number mean and what do the differences in the numbers mean? And
unless my numbers and your numbers have nothing to do with one another nor the
numbers of anyone else they need to have some shared models and references.

Defining these would, I think, be more difficult (and long winded) than
creating a common service monitoring network and metrics (which would evolve
over time in response to shared experiences).


On Thu, 15 Apr 2010 09:51:48 +0100, John Harrison wrote
> On Wed, 2010-04-14 at 23:06 +0100, Peter Noerr wrote:
> 
> > What I'm really questioning is whether a zeerex response from a Source is
the right place for this information - whatever it is.
> 
> Mike's original request/proposal was to add an index for some 
> measure of reliability/responsiveness to the ZeeRex context set -
>  NOT the ZeeRex record schema.
> 
> I've not seen any convincing arguments against this - in fact the
> conversations about how such a measure of reliability/responsiveness
> might be calculated seem to indicate that this would be useful.
> 
> John
> 
> > In one very real sense it is the right place, because then each Source can
decide for itself if it wants to obtain and make available this information.
But then each Source has to set up some external measuring point to get the
information, and the method of getting it back, and storing it. Not difficult,
but another thing to set up, maintain and manage. 
> > 
> > To make this easier it might be interesting to consider a "query mirror"
server, which the Source could send a query message to, and which would bounce
the message back to the Source. The dumber it is the better, so the Source can
handle its own authentication and API/protocol/language issues with the mirror
needing to know nothing about them. And a dumb query mirror could be easily
deployed at many locations to handle traffic for many Sources. Possibly as a
SRU server add-on? (The old psychiatrists joke "You're fine, how am I?" comes
to mind.)
> > 
> > Peter
> > 
> > 
> > > -----Original Message-----
> > > From: SRU (Search and Retrieve Via URL) Implementors
> > > [mailto:[log in to unmask]] On Behalf Of Edward C. Zimmermann
> > > Sent: Wednesday, April 14, 2010 6:46 AM
> > > To: [log in to unmask]
> > > Subject: Re: Add "reliability" index to CQL's "zeerex" context set
> > > 
> > > That's the point of "global" service monitoring...
> > > 
> > > Running search to ones own targets in ones own networks does not need
> > > it.. but
> > > also it a club house.. ZeeRex/Explain is about going beyond the private
> > > club.
> > > 
> > > On Wed, 14 Apr 2010 09:01:15 -0400, Ross Singer wrote
> > > > On Wed, Apr 14, 2010 at 6:51 AM, Mike Taylor <[log in to unmask]>
> > > wrote:
> > > > > Peter, we didn't envisage this as something that servers self-
> > > report,
> > > > > but as something measured from the outside.  To a client, it's
> > > > > irrelevant whether a server is running off a UPS, for example: all
> > > we
> > > > > care about is whether we can contact and search in and retrieve
> > > from
> > > > > the server.
> > > >
> > > > On the flip-side, though, if something's wrong between you and that
> > > > particular service (let's say a DNS server in your network goes
> > > > haywire and intermittently forgets certain domains, or something),
> > > > this service's reliability is tarnished through no fault of its own.
> > > > Or, let's say, for example, your ISP has decided that service X
> > > > hasn't paid enough of a toll to get priority to its customers...
> > > >
> > > > -Ross.
> > > 
> > > 
> > > --
> > > 
> > > Edward C. Zimmermann, NONMONOTONIC LAB
> > > Basis Systeme netzwerk, Munich Ges. des buergerl. Rechts
> > > http://www.nonmonotonic.net
> > > Umsatz-St-ID: DE130492967
> -- 
>               '.    ,'.         John Harrison
>              '  `  '  '         University of Liverpool
>  c h e s h i r e  |  3          e: [log in to unmask]
>                   v             w: www.cheshire3.org
>               `-..;.'           t: 0151 7954271
>                 ..,     (c)


--

Edward C. Zimmermann, NONMONOTONIC LAB
Basis Systeme netzwerk, Munich Ges. des buergerl. Rechts
http://www.nonmonotonic.net
Umsatz-St-ID: DE130492967

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