[Seaside] Strategies for bulky renders/updates

Philippe Marschall philippe.marschall at gmail.com
Sun Mar 13 10:44:31 UTC 2011

2011/3/13 radoslav hodnicak <rh at 4096.sk>:
> I've been using seaside with jquery to create quite interactive
> interfaces, using the simplest approach of "everything has its own
> callback". This works well if the dataset you're working with is
> small, but I'm now venturing into territories where it takes seconds
> to receive+render a page, which isn't acceptable.
> For an example of what I'm talking about imagine a page showing a list
> of emails. Every line (email) has a clickable sender, subject, date,
> and a bunch of more actions and icons etc. If you're creating
> anchors/click actions for each field separately, that's easily
> hundreds or thousands of callbacks per page, each needing to be
> generated on the server and sent over the wire. So clearly I need to
> instead write client side javascript that will figure out what the
> user clicked and do a parametrized request. Which I can do, but I'm
> wondering if someone has figured out a clever way how to map the
> information on the page to smalltalk objects on the server (other than
> using callback registry). Same goes for bulk actions involving
> multiple items ("delete selected" and the like).

I don't think there's an alternative. Unfortunately callbacks are
currently hard wired to read only one request field. In addition if
you move the code to a request handler it is hard to access the
session from there :-(


More information about the seaside mailing list