[OASIS Issue Tracker] (COEL-12) Might need a look before you leap function for large atom downloads.

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

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

Paul Bruton edited comment on COEL-12 at 3/8/16 2:31 PM:
---------------------------------------------------------

Discussed by David, Paul, Matt.

We agreed to change the query response so that a Data Engine MAY return a URL that the client can use to pull the atoms at a later point, page by page, instead of returning the atoms themselves.

The alternative response MUST have a URL, a ready-at time and an expiry time. The DE is declaring that the atom download is being prepared, will be available at the URL after ready-by time and will no longer be available after expire time. 

This allows the DE to schedule compute power for a better time and recognises that these are rare, unusual events.

If the SP changes its mind and decides not to download the data, there is no means to tell teh DE, which will go ahead and prepare the data anyway. We did no consider this a problem.





was (Author: paul.bruton):
Agreed that the DE MAY return a URL that the client can use to pull the atoms separately, page by page.

We also discussed how the data engine MAY return a URL for the atoms, to be available at a later point with a time specified. this allows DE to schedule compute power for a better time and recognises that these are rare, unusual events.

How long is the data available for? Can the SP say 'I've changed my mind' and discard the request? (leave this out and just put an expiry on the data).







> Might need a look before you leap function for large atom downloads.
> --------------------------------------------------------------------
>
>                 Key: COEL-12
>                 URL: https://issues.oasis-open.org/browse/COEL-12
>             Project: OASIS Classification of Everyday Living (COEL) TC
>          Issue Type: New Feature
>            Reporter: David Snelling
>            Assignee: Paul Bruton
>            Priority: Minor
>
> The DE should potentially have an ‘offline’ approach (or double check) for ‘all atoms’ requests from Service Provider to Data Engine. This is to protect from too large a message and to improve the implementation of RPE. The later means this issue needs some discussion.



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