Yes, it does run counter to basic REST principals but there are valid
practical reasons why someone would want this. One of the example
Atompub services, for instance, uses a per-session in memory store. I
don't think it's something we should be recommending but I think it's a
good idea to at least make it available.
- James
David Primmer wrote:
Can someone explain to me again why you'd want server side session support
in abdera? It seems anti-ethical to REST principles.
davep
On Feb 7, 2008 7:24 AM, James M Snell (JIRA) <[EMAIL PROTECTED]> wrote:
[
https://issues.apache.org/jira/browse/ABDERA-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566634#action_12566634]
James M Snell commented on ABDERA-84:
-------------------------------------
Right, which was a bug because the session wasn't being created. The bug
was fixed and it should be working now.
Server side session management support
--------------------------------------
Key: ABDERA-84
URL: https://issues.apache.org/jira/browse/ABDERA-84
Project: Abdera
Issue Type: New Feature
Reporter: Deepal Jayasinghe
Fix For: 0.4.0
I am implementing a client server application using abdera and I need to
maintain a session in the server side , simply I need to keep a value in the
session across multiple requests. When I looked at the code I did not find a
way to do that, so it would be great of we can add the HttpServletRequest in
to the RequestContext . Then I can store value in the HttpServletRequest
and use that.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
