[
http://jira.jboss.com/jira/browse/JBSEAM-2105?page=comments#action_12382880 ]
Norman Richards commented on JBSEAM-2105:
-----------------------------------------
I don't understand what security issue you are referring to, but a globally
incremented converstion id counter would expose MORE information to the outside world
about what is happening on the server. That can't be a good thing.
pluggable conversation id strategy
----------------------------------
Key: JBSEAM-2105
URL:
http://jira.jboss.com/jira/browse/JBSEAM-2105
Project: JBoss Seam
Issue Type: Feature Request
Reporter: Norman Richards
Fix For: 2.0.1.GA
Attachments: patch_file
Conversation id generation should be managed by a component that can be overridden for
specific deployments. We might even consider providing a more interesting default (or
optional) strategy like a GUID.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira