Alessandro Vernet wrote:
> Nikola,
>
> On 9/27/07, Nikola Radic <
[hidden email]> wrote:
>> In the environment with min. 100 concurent users, Ethernet and CPU will be
>> more than busy.
>> Any way to prevent this behaviour?
>
> Yes, of course, I understand. At this point you can't get around this.
> But this is definitely an optimization that we'd like to implement.
The deep reason why many Ajax events are sent to the server is that all
the XForms event handling is implemented on the server. Such events
include value changes, clicks, and focus changes. Currently, we do not
optimize this and will tell the server about things occurring on the
client even if, for example, there are no related event handlers anyway.
This is clearly where some optimizations could be done to reduce traffic.
Note that we already optimize Ajax events by grouping events into single
Ajax messages. For example if you tab fast between fields then you will
see a single Ajax message sent after a while instead of just one per tab.
-Erik
--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/--
You receive this message as a subscriber of the
[hidden email] mailing list.
To unsubscribe: mailto:
[hidden email]
For general help: mailto:
[hidden email]?subject=help
OW2 mailing lists service home page:
http://www.ow2.org/wws--
You receive this message as a subscriber of the
[hidden email] mailing list.
To unsubscribe: mailto:
[hidden email]
For general help: mailto:
[hidden email]?subject=help
OW2 mailing lists service home page:
http://www.ow2.org/wws
Locked
