[MOBY-dev] Paging mechanism

[Javier de la Torre]

Hi Martin,

Would be nice. For the time being I have created a new service type
under Retrieval called TapirProvider and I will register all my
services with this service type. All of them will support he paging
mechanism.
I think we need a better name for this than TapirProvider, but couldnt
think of anything better.

Here is the description for this Service Type:
----
TAPIR providers are normally biological collection databases. The most
common operation is to retrieve data from them to be used in analysis.
They always implement two secondary inputs, a start and next parameter
to do paging. Please read
http://trac.pywrapper.org/pywrapper/wiki/BioMOBYSupport
---
At least if you are constructing a client to query all these services
that support paging you know hot to get to them.

If you dont mind I have changed the parameter names to start and next
so that it fits with the TAPIR specifications.

Javier.


On 9/27/06, Martin Senger <martin.senger at gmail.com> wrote:
> Javier wrote:
>
>
> > What I am more interested now is on another topic. If you remeber
> > Mark we discussed more than one year ago the need for a paging
> > mechanism for our services in BioMOBY. Now that I am implementing
> > this I took Martin Singer approach to include this functionality on
> > the service: the services always have a two parameters: maxPages and
> > startPage that are used for paging...
>
> I am interested, as well. I used two secondary parameters because it was an
> immediate solution. But we should think about it now in the same way as we
> did with asynchronous invocation, meaning to put this information in an
> envelope (BioMoby or SOAP) - as Javier already proposed. Could anybody more
> familar with these envelopes suggest where to put it please? Actually, make
> a real RFC for it...
>
> Thanks,
> Martin
>
> --
> Martin Senger
>    email: martin.senger at gmail.com
>    skype: martinsenger