Re: Advice on mod_lisp-based web application.

(message (Hello 'Blaine)
(you :wrote :on '(23 Apr 2007 11:22:48 -0700))
(

B> The beta works fine for one user, but, understandably, it doesn't work
B> for
B> multiple users.

hmm, since HTTP is stateless protocol it's kinda hard to make single-user
application with it..
unless it's something extremely special, it should be very easy to convert
it to multi-user -- if you have state in some global variables, move them to
session variables etc. it should be lots easier than dealing with
'persistence' and 'termination' delirium you're describing below.

the only thing i can imagine that makes it's hard to make multi-user
application is having some calculations running persistently in the thread..
but to serve web requests in such situation you need multithreading anyway,
so adding more users should be straightforward -- spawn more threads..

B> As for the Persistence issue, I was thinking I could use remote-ip-
B> address
B> key/value pair that comes with every modlisp request to identify the
B> user.
B> Will this work, or will I have to do something with cookies?

cookies is a standard way of doing this kind of things. i think it's always
better to use standard things.
there's also another technique for this that works everywhere -- put session
info (session id or whatever) into URLs.

B> close out the user's "session". I'm not sure this is an appropriate
B> use of
B> the condition system, and furthermore, I don't know where I would put
B> the
B> handling code (a handler-bind form, I belive).

as you describe, you're using HTTP protocol in a stateful fashion, and
moreover you can send info from server to client even if client isn't
requesting it.. how?
certainly there's stuff like AJAX, but you haven't mentioned it..

)
(With-best-regards '(Alex Mizrahi) :aka 'killer_storm)
"I am everything you want and I am everything you need")


.

Relevant Pages