RunID - cross service tracking

[Guy Rixon]

Wil,

this probably _should_ be part of the support interfaces, since (presumably)
we want it supported eventually on all services.

If we make it a SOAP header, then its mustUnderstand attribute should be set
false.

If we make it an extra agument on CGIs, then presumably it's ignred by
default.  We should probably put a stipulation in the support-interfaces spec
that all IVO services must allow this argument even if they ignore it.

What exactly is the servename part?

It seems useful to have one ID associated with many related calls to services:
i.e.  with a job rather than a job-step.  Was this what you intended?

Cheers,
Guy

On Thu, 23 Sep 2004, Wil O'Mullane wrote:

> Hi All,
> Not sure where to go with this idea. I have added it to a new draft of Support Interfaces but that is not the proper place to do this.
> In a meeting we had yesterday to discuss logging
> Tim Kimball had an interesting idea. We should have a RunID associated with
> a particular service run.
> So a portal creates a run id in the form servename:sequentialNum. This id should be passed to all services called such that it is logged for each service call. Any service calling another service should pass this number on. Hence if DataScope calls 300 services from one user request they should all have the same RunID. For a web Service the run id could be in the header i.e. no change to the interface. For the Simple GET services it can simply be appended as &RunID=server:990990 which will automatically put it in the log.
>
> Hence the tie to the logging interface.
>
>
>
> wil
>

Guy Rixon 				        gtr at ast.cam.ac.uk
Institute of Astronomy   	                Tel: +44-1223-337542
Madingley Road, Cambridge, UK, CB3 0HA		Fax: +44-1223-337523