[Cosmo-dev] Dashboard Server Requirements Meeting
Ted Leung
twl at osafoundation.org
Tue May 15 17:38:35 PDT 2007
On May 15, 2007, at 1:37 PM, Bobby Rullo wrote:
> Hi all,
>
> This morning Matthew, Brian, Randy and I had a meeting to bring the
> client and server team to some sort of agreement on how client/
> server interaction will work for dashboard. Here are the main
> points that came out of that meeting (or at least my interpretation
> of them ;-) ) Some of this stuff affects design so I will post
> another message to the design list.
>
> 3 Queries
> --------------
> * There client will be required to make three queries to get the
> dashboard data - one for NOW, one for LATER and one for DONE. Each
> will have different parameters that can be set
I'm not sure I follow the reasoning behind having 3 distinct
queries. Are we ever really going to be able to only issue one of
these 3 queries? At any given moment, items can move between 2 of
the sets -- will we always be able to predict what those 2 sets will be?
>
> Auto-Triaging
> --------------------
> * There will be no timer on the client which automatically triages
> items which have moved into the NOW timeframe
> * A sort of auto-triaging does happen in that when a query is made
> and the client gets back events that are happening NOW it will ping
> back the server to update the triage.
Is this a schedule thing, or a result of some other limitation?
Ted
More information about the cosmo-dev
mailing list