Comments on: Tracker’s class signals, live search capabilities

By: Crisanta

Crisanta — Thu, 25 Nov 2010 00:26:30 +0000

Holaaaaaaaaaaaaaaaa

By: Urho Konttori

Urho Konttori — Fri, 20 Mar 2009 08:23:39 +0000

@alexander:
Well, the fact is that for live query support the server would anyway need to run the same query, but in addition, also the server would need to keep the session alive for the live query so that the change damage map can be properly calculated, so processing wise, this is probably better solution, as application can at least now decide when it needs to refresh the content. Also, any removals are really easy for the app to do, and so are changes (you can just re-query the changed content). Additions tend to require a bit more logic if the sorting is done on server side. If the sorting is done client side, even the additions are easy to do (you just rerun the same query again with the additional filter that it only applies to the added items).

By: Alexander Larsson

Alexander Larsson — Thu, 19 Mar 2009 17:06:42 +0000

Hmm, this seems like a kind of heavy way to implement live queries. Clients basically have to rerun the query in a polling fashion everything anything changes, pulling down all the data again.

I guess if you just want to display “last 10 emails” its ok, but that sort of usecase seems pretty limited.