[SISCweb] Session attributes vs SRFI-39 parameters

Hello,

Now that SRFI-39 parameters can be used instead of session attributes,
I find myself wondering what advantages one approach has over the
other, or whether SRFI-39 parameters really are a good idea at all for
a SISCweb application.  Alessandro, could you maybe contrast the two
approaches?

Also, I do not understand the following quote (from
http://siscweb.sourceforge.net/docs.html):

"SRFI-39  parameters are a valid alternative to session attribute for
tracking state in SISCweb when not using the strict continuation-based
approach (i.e. send-*/[suspend|forward]."

And the AJAX Counter example (counter.scm, from CVS rel-0-4-dev) has
the following comment:

  ;; "session" variable; note that it becomes "per user" (sort of)
  ;; only if parameterized at the application entry point; otherwise
  ;; it would be shared among all users
  (define *N* (make-parameter 0))

I understand the need to parametize, but what do you mean by becoming
a *sort of* per user parameter? When would it not be a per user
parameter? Is it because the user would get a "new" parameter if he
somehow navigated through the application entry point again?

Thanks in advance!

Best Regards,

Victor Rodriguez.

p.d. SISCweb is great!


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642