You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Igor Drobiazko (JIRA)" <ji...@apache.org> on 2010/01/13 21:27:54 UTC

[jira] Commented: (TAP5-985) Implement sessionless strategy for Form component's ValidationTracker

    [ https://issues.apache.org/jira/browse/TAP5-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799914#action_12799914 ] 

Igor Drobiazko commented on TAP5-985:
-------------------------------------

Isn't it a duplicate? Have a look at TAP5-979.

> Implement sessionless strategy for Form component's ValidationTracker
> ---------------------------------------------------------------------
>
>                 Key: TAP5-985
>                 URL: https://issues.apache.org/jira/browse/TAP5-985
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.1.0.0, 5.1.0.1, 5.1.0.2, 5.1.0.3, 5.1.0.4, 5.1.0.5, 5.1.0.6, 5.1.0.7, 5.0.15, 5.0.16, 5.0.17, 5.0.18, 5.0.19
>            Reporter: Kalle Korhonen
>
> High traffic sites with high number of unauthenticated users consume huge amounts of memory if form component is being used because of ValidationTracker causes creation of user's session when form returns errors. The issue is being discussed at http://www.mail-archive.com/users@tapestry.apache.org/msg41721.html. Sounded like Howard had some idea for creating a sessionless validationTracker and also Josh Canfield had created a solution for T5.0.x.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.