Re: LISP for web

Marco Baringer wrote: 
(i really can't believe i forget to mention this)

there is one other thing which will become much easier if we take over
control of executing actions: serializing session state and, thanks to
this, ucw session mobility. atm everything in a session is easily
(fsvo easy) serializable except the anonymous closures which are
generated by the cps transformation and stored in the components. if
we stop using the lisp's functions object but create our own which
consits of: code [another set of clos objects] and the environement
[again a clos object] then sending the entire session over the wire
becomes doable.

Ideas on how to store this information centrally for all of the app servers? I would love to see either a RDBMS (Postgres) or Memcached (http://www.danga.com/memcached/) option.


currently if you need to run a ucw app on multiple machines your only
option is to tie a session to a particular machine and map all
subsequent requests to that machine. this kind of setup is easy to
create and works fine, but it has the major defect that if the machine
goes down it takes all of its sessions with it. i don't know what most
people think about this but the only client i have who would like to
run the site on multiple machines wants a hardware failure to be as
transparent as possible.

This would allow me to use UCW not only in personal projects, but at work as well. Any timeline? I can do some testing, although I'm a bit of a newb.

BA
.

Relevant Pages

  • Re: LISP for web
    ... serializing session state and, ... > this, ucw session mobility. ... > (fsvo easy) serializable except the anonymous closures which are ... > we stop using the lisp's functions object but create our own which ...
    (comp.lang.lisp)
  • Re: LISP for web
    ... this, ucw session mobility. ... code [another set of clos objects] and the environement ... Ring the bells that still can ring. ...
    (comp.lang.lisp)