[Cosmo-dev] abbreviating content of entries in atom collections

[Travis Vachon]

I think this is definitely going to be desirable in the future, but  
I'm not sure how difficult it would be to integrate into the current  
ui and dashboard. While I'm sure it wouldn't be _too too_ much work,  
it sounds like it could be risky for 0.7.

That said, we could certainly implement it on the server side as long  
as the current /full projection did not change, and work the client  
side details out at our leisure.

-Travis

On Jun 11, 2007, at 10:53 AM, Brian Moseley wrote:

> at the moment, when a client requests a feed for an item collection,
> each entry in the feed contains the entire representation of its
> associated item. this is a pretty hefty amount of data for even just
> your basic event item. i wonder if clients actually need the entire
> item state in this instance? when the web ui renders the dashboard
> view or calendar view based on the contents of a feed, what specific
> data does it require?
>
> maybe we could define a slimmer item representation that's just used
> in feed content (maybe one for dashboard feeds and one for calendar
> feeds). then, when the ui needs to populate the detail view, or to
> refresh the calendar or dashboard based on an item update, it can
> request the item entry directly, which would return the entire state
> of the item.
>
> this is analogous to the traditional mail client, which fetches a few
> headers for each message to populate its list view and then pulls down
> an entire message to populate its detail view.
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev