Hey everyone, so a quick set of questions on a few things that I noticed that do not seem to make sense and would like someone's input one.
1- After starting a weblocks application say (testweb:start- testweb :port 3223) all other applications I start are automatically started at the same port irrespective of the port number I provide. I am not sure why this is taking place but I checked the start-testweb and the code is (apply #'start-weblocks args) (start-webapp 'testweb)) which would mean that the port (which is in the args) is going to the whole weblocks and not just this app. Anyone faced this or am I missing anything? 2- Attempting to stop any weblocks application results in a drop to the debugger with the reason being that the variable HUNCHENTOOT:*ACCEPTOR* is unbound. Note though that the application does stop being served. 3- Attempting to do (weblocks:reset-session) also throws that the variable HUNCHENTOOT:*ACCEPTOR* is unbound. As far as i can tell though the session is not reset. On the point of sessions can there be a page that is not dependent on the session so that if an issue takes place the user is not stuck. Appreciate the feedback that you can provide. Regards, Mackram --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
