[hunchentoot-devel] Re: session shearing question

[Andrea Chiumenti]

Hello,
this morning, when I woke up, taken from curiosity, I've opened hunchentoot
code to inspect how sessions are handled.
I've seen that session modifiers are all protected with the WITH-LOCK form,
now my question is *session-data* common to
all hunchentoot servers instantiated on the same lisp instance ?

Another question, now suppose we have in a single hunchentoot server serves
two applications ( distinguished by their path ).
It seems that hunchentoot shares the session between  these two, and
sometime it's good, but what should I do if I want applications to share
different sessions ?

On Jan 5, 2008 12:01 AM, Andrea Chiumenti <kiuma72 at gmail.com> wrote:

> Ok,
> you convinced me.
> For now I can use elephant for my cl-webobjects project.
> Then I could hack swarmcache (http://swarmcache.sourceforge.net/)
> and port it to lisp (if I gain a bit more experience in CL coding)
>
>
> On Jan 4, 2008 11:27 PM, Volkan YAZICI <yazicivo at ttmail.com> wrote:
>
> > "Andrea Chiumenti" <kiuma72 at gmail.com> writes:
> > > to have a process safe server, both cl-perec and elephant use a non
> > > pure lisp solution :(
> >
> > So you shouldn't be using HTTPS with hunchentoot too, 'cause it
> > depends on a foreign ssl library. That's the trade. But you may want
> > to chose waiting for somebody to implement an ACID compliant storage
> > framework in lisp -- with tons of other indexing, concurrency, data
> > integrity stuff. (By the way, there exists commercial solutions. See
> > AllegroCache for instance.)
> >
> > On the other hand, IIRC elephant could use Berkeley DB as a
> > backend. AFAICS, probability of finding libdb installed on a system is
> > much more higher than finding libssl installed.
> >
> >
> > Regards.
> > _______________________________________________
> > tbnl-devel site list
> > tbnl-devel at common-lisp.net
> > http://common-lisp.net/mailman/listinfo/tbnl-devel
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/tbnl-devel/attachments/20080105/d21493ad/attachment.html>