[
https://issues.apache.org/jira/browse/TOMAHAWK-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12580077#action_12580077
]
Ernst Fastl commented on TOMAHAWK-1214:
---------------------------------------
Sound like a cool feature. There are 2 things which I do not yet completely
understand:
1.) What is the event which leads to the storage of the form data in the queue
-a button which is clicked?
-every time a value of one of the inputs changed?
2.) What is the "acting" component which submits one set of queue? what should
happen after that?
-just updateModel?
-actionListener or action?
-will be done by valueChangeListeners of the input components?
could also be that I misunderstood the idea - in any case - further
clarification would be nice :-)
> allow to process form submits in a queue for high-speed input handling
> ----------------------------------------------------------------------
>
> Key: TOMAHAWK-1214
> URL: https://issues.apache.org/jira/browse/TOMAHAWK-1214
> Project: MyFaces Tomahawk
> Issue Type: New Feature
> Components: PPRPanelGroup
> Reporter: Mario Ivankovits
> Assignee: Ernst Fastl
>
> Enhance the PPR stuff in a way which allows to process form input asynchron
> in a queue for high-speed input handling.
> Probably by adding a new attribute to the PPRPanelGroup called
> "queued=true|false". With "true" the form data should be collected and held
> in a queue on client side.
> The client then checks that queue at given intervalls (queueCheckInterval=)
> if there is data in the queue and transmit that data to the server like a
> normal ppr request. Between each transmit a queueWaitInterval= should be
> waited.
> A status component (queueShowStatus=true|false) should show the success of
> each transmit. A client side javascript should be used to extract the status
> text information from the form data
> (queueShowStatusInfoBuilder=javascript-method-name(formData))
> The PprPanelGroup should also be enhanced to being able to point to the
> messages component (messages=component-id) the queueStatus information should
> then be able to visualize that text and show e.g. a red-cross if there were
> errors (=messages)
> For this first version the status info can be a simple table created
> client-side using some css to allow to format it according to the application
> skin.
> A simple table with two columns
> status-info|return-visualization
> status-info is the text returned by the queueShowStatusInfoBuilder javascript
> method and return-visualization might be an icon.
> Only waiting requests and those with errors should be shown, correctly
> finished requests can be removed from the list.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
