Hello,
it looks like to me from the demos, whenever I move the focus from one control to another, the javascript is communicating with server. This looks perfectly fine when the control content has been changed and the bounded data have any validation bounded to it or perhaps the control has some triggers. But if these conditions are not satisfied, what is the reason to communicate with the server? Unnecessary communication seems like waste of client, server and network resources. thanks Zdenek -- 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 |
[hidden email] pisze:
> Hello, > > it looks like to me from the demos, whenever I move the focus from one control > to another, the javascript is communicating with server. This looks perfectly > fine when the control content has been changed and the bounded data have any > validation bounded to it or perhaps the control has some triggers. But if these > conditions are not satisfied, what is the reason to communicate with the > server? Unnecessary communication seems like waste of client, server and > network resources. > > thanks > > Zdenek > you are not right, Orbeon must handle many xforms events, like xforms-focus for example. Communication is needed here. Peter -- 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 |
Hi,
thanx for answer. Will xforms-focus event handling done on server result always in some state updates ? Zdenek -----Original Message----- From: Piotr S'wigon' [mailto:[hidden email]] Sent: Thursday, August 14, 2008 10:57 AM To: [hidden email] Subject: [ops-users] Re: unnecessary client-server communication [hidden email] pisze: > Hello, > > it looks like to me from the demos, whenever I move the focus from one control > to another, the javascript is communicating with server. This looks perfectly > fine when the control content has been changed and the bounded data have any > validation bounded to it or perhaps the control has some triggers. But if these > conditions are not satisfied, what is the reason to communicate with the > server? Unnecessary communication seems like waste of client, server and > network resources. > > thanks > > Zdenek > you are not right, Orbeon must handle many xforms events, like xforms-focus for example. Communication is needed here. Peter -- 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 |
Administrator
|
In reply to this post by zdenek.hrib
A couple of reasons:
1. handling of DOMFocusIn and DOMFocusOut 2. adjustment of the current repeat index when in a repeat Re #1, this could certainly be optimized when there are no handlers. -Erik On Aug 13, 2008, at 10:16 AM, [hidden email] wrote: > Hello, > > it looks like to me from the demos, whenever I move the focus from > one control > to another, the javascript is communicating with server. This looks > perfectly > fine when the control content has been changed and the bounded data > have any > validation bounded to it or perhaps the control has some triggers. > But if these > conditions are not satisfied, what is the reason to communicate with > the > server? Unnecessary communication seems like waste of client, server > and > network resources. > > thanks > > Zdenek 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 |
Administrator
|
In reply to this post by Hřib Zdeněk
Not necessarily.
There may be no handlers for the events, or there may be handlers that don't cause change to state. -Erik On Aug 14, 2008, at 4:56 AM, Hřib Zdeněk wrote: > Hi, > > thanx for answer. Will xforms-focus event handling done on server > result always in some state updates ? > > Zdenek > > > -----Original Message----- > From: Piotr S'wigon' [mailto:[hidden email]] > Sent: Thursday, August 14, 2008 10:57 AM > To: [hidden email] > Subject: [ops-users] Re: unnecessary client-server communication > > [hidden email] pisze: >> Hello, >> >> it looks like to me from the demos, whenever I move the focus from >> one control >> to another, the javascript is communicating with server. This looks >> perfectly >> fine when the control content has been changed and the bounded data >> have any >> validation bounded to it or perhaps the control has some triggers. >> But if these >> conditions are not satisfied, what is the reason to communicate >> with the >> server? Unnecessary communication seems like waste of client, >> server and >> network resources. >> >> thanks >> >> Zdenek >> > Hi, > > you are not right, Orbeon must handle many xforms events, like > xforms-focus for example. Communication is needed here. > > Peter > > > > -- > 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 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 |
Free forum by Nabble | Edit this page |