Re: [Digir-dev] Re: DiGIR development at CRIA

[Ricardo S. P. <ri...@cr...>]

   Hi, all,

    Back to the heartbeat checks.

    As Dave and Stan mentioned, heartbeat checks should not be
implemented as a main protocol service.
    I assume that this means that the heartbeat requests will not be
included on the main XML schema for requests and responses.
    The way I see it, we would implement a new type of "action" (HTTP
GET action=3Dstatus parameter) and maybe an XML document on the "doc"
parameter to specify possible arguments for the heartbeat request. Is it
necessary to provide more information on the heartbeat request, such as
what kinds of tests are to be performed or which providers to check?
    This would be implemented completely within the portal, as PJ
described. The response would be another XML document describing the
results of all checks performed, for each provider checked.
    The checks to be performed would be those that Dave listed on an
earlier message, that I copy below.

1. Is there is a network connection to the machine.
2. Is the HTTP service running?
3. Is the DiGIR service responding?
4. Is a particular resource available on the DiGIR service?
5. What is the current load on the DiGIR provider service?

    #5 can be implemented just by returning the time elapsed between the
request is submited to provider (metadata request) and response
(returned by the provider).

    Does it sound like a plan?
    All the best,

Ricardo

--
Ricardo Scachetti Pereira
Gerente de Pesquisa
Centro de Refer=EAncia em Informa=E7=E3o Ambiental - CRIA
http://www.cria.org.br/



--
This message has been scanned for viruses and
dangerous content and is believed to be clean.