[OASIS Issue Tracker] (COEL-68) Server status request

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/COEL-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63064#comment-63064 ] 

Paul Bruton commented on COEL-68:
---------------------------------

I think this is a good idea, however it is a little different for the data engine (as compared with the IDA) in that there are three different services and each may be on different servers: PQI, MMI and BAP. It's quite reasonable to assume tha the MMI might be down for maintenance but the BAP still runnning. In this case who are we asking about the status? Does the API in 2.2.1 of the BAP have the highest SLA of all - in other words it is the last to go down? Or does each service provide its own status.

The reasoning behind Joss's request is to have something easy and quick to call to check somebody is at home before formulating a more complex request, or perhaps to provide a visual feedback to a user of the service providers system. In that case I would expect the status request to be on the same server as the service it is reporting against: IOW we would have three. 

Joss: Can you share the description of the packet you return please?

> Server status request
> ---------------------
>
>                 Key: COEL-68
>                 URL: https://issues.oasis-open.org/browse/COEL-68
>             Project: OASIS Classification of Everyday Living (COEL) TC
>          Issue Type: New Feature
>            Reporter: Joss Langford
>
> We have implemented a status request on the Activinsights' server that returns version number (integer), server name (string) and server time (UTC). It might be very useful to have something similar on the IDA and Data Engine – otherwise we’ll be tempted to send a dummy request on one of other calls to check someone is home.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)