--
You received this message because you are subscribed to the Google Groups "Lift" group.
To post to this group, send email to lif...@googlegroups.com.
To unsubscribe from this group, send email to liftweb+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
Why bother with StatelessBehavior? Why not just an API to test if the current request is stateless?
Also perhaps the parameterless def behavior should not have the empty parameter list?
I glossed over your point about cookies.
So, if one wanted users to be stateless until some action took place
you could:
a. mark all requests as stateless by default
b. if the user takes some action, then give them a cookie
c. mark future requests as stateful if the cookie is present
so I'm just thinking this through.. imagine:
- request comes in, no cookie present, mark it as stateless
- process the request, determine its a request to store some state and
hence initiate a session
- now, we cannot store that state in the session, because we're
already stateless
--
You received this message because you are subscribed to the Google Groups "Lift" group.
To post to this group, send email to lif...@googlegroups.com.
To unsubscribe from this group, send email to liftweb+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
On Tue, Aug 23, 2011 at 6:47 PM, Naftoli Gugenheim <nafto...@gmail.com> wrote:Why bother with StatelessBehavior? Why not just an API to test if the current request is stateless?
There's already an API to test. The problem is that wrapping an "if (stateless) xxx else normal behavior" around lots of code takes a lot of time and is error prone and messes up the code.
Also perhaps the parameterless def behavior should not have the empty parameter list?
Then you get into the "is this a partially applied function or a method call" quandary.
--
You received this message because you are subscribed to the Google Groups "Lift" group.
To post to this group, send email to lif...@googlegroups.com.
To unsubscribe from this group, send email to liftweb+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
How about you go and update the names and any other method signatures that you think need improvement? I am less than optimal at naming and am happy to have improvements.
This is OT, but how are you generating that diff output? That's
pretty nifty (sort of like a b/w version of --color-words).
Thanks,
Pete
Thoughts?
--You received this message because you are subscribed to the Google Groups "Lift" group.
To post to this group, send email to lif...@googlegroups.com.
To unsubscribe from this group, send email to liftweb+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
Pete