[Design] [cosmo] Server Restraints and the Dashboard

Mikeal Rogers mikeal at osafoundation.org
Tue May 15 14:24:39 PDT 2007


On May 15, 2007, at 1:51 PM, Bobby Rullo wrote:

> Hi there,
>
> Due to the nature of Cosmo UI as a web application, we have  
> identified a few areas where we find it helpul to put in some  
> constraints that don't exist on the desktop for reasons of server  
> load, bandwidth and performance.
>
> One of these constraints is the nature of the LATER section.  
> Getting a single occurrence for every recurring event in the future  
> could be an expensive query with lots of results that the user  
> probably doesn't want (the "birthday" phenomenon is a good  
> illustration of this - do we really need to see every single  
> birthday in the next year in the later section?) Setting an  
> arbitrary yet reasonable limit could help things out here - maybe a  
> month or so into the future.
>
> Similarly, expanding every single recurring item from now to the  
> beginning of time to get every DONE occurrence is taxing on  
> bandwidth and server load. Putting a limit on how far to go back  
> (say, one month back) would be very helpful.

We could do like google reader does.

Get a set amount of later items, 20 or 30, then when the user scrolls  
near the bottom of those items we send another query for another 20  
or 30 and load them in dynamically.

-Mikeal

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.osafoundation.org/pipermail/design/attachments/20070515/401f0fb2/PGP.pgp


More information about the Design mailing list