[Seaside-dev] Some Feature Requests

[Julian Fitzell]

On Tue, Oct 28, 2008 at 10:22 AM, Keith Hodges <keith_hodges at yahoo.co.uk> wrote:
> I haven't looked at 2.9 yet but I would like to request a couple of
> essentials.
>
> 1. Please could you at least add a properties dictionary to WASession.
> This is extremely useful, and allows multiple features to be added to
> Seaside as plugins/addons/helpers without subclassing WASession.

Would you expect such a dictionary to be backtracked or not? I think
this would be the trickiest part of this. The helpers you are thinking
of might also work better as RequestFilters, which are new in 2.9.
Could you elaborate a bit more here with some examples?

> 2. I would like you guys to review the helpers in SeasideJetsam, this
> kind of thing should be included as standard, again they work very well
> indeed.
>
>    i.e. add shore components support to any seaside app, magma, comet,
> keep alive, (glorp from VW equivalent of helpers) etc etc.
>
> 3. Please could you add support for post request processing.
>
> i.e. enable code to run after the server has sent the request to the
> browser, in the same thread.
>
> e.g.
>
> removeItem: item id: id on: script
>
>    script effect id: id; dropOut.
>
>    "remove item from the database,
>        a) without slowing the UI interaction
>        b) within the scope of this session/db session etc"
>
>    self session postServeBlocks add:  [ self removeItem: item ] .

I can see how this would be useful. If you want it to run in the same
process, the process monitor would have to deal with it, which is
unfortunately pretty hairy code. :) We currently guarantee that only
one process is executing within a session at a time. Maintaining this
guarantee while allowing the incoming process to resume will be
somewhat messier, but certainly not impossible. But does that offer a
significant benefit over simply using a streaming HTTP server so that
the response is being streamed as it is generated?

Julian