- From: David Landwehr <DLandwehr@novell.com>
- Date: Fri, 29 Apr 2005 08:20:31 +0200
- To: <fora@annevankesteren.nl>,<mark.birbeck@x-port.net>
- Cc: <www-forms@w3.org>
Hi Mark, I'd like to comment on your following statement: > I would say that anyone building portals and intranets -- applications that > pull data from a number of sources -- will get immediate benefit now from > XForms if they put in the effort to switch over. Data can then be pulled > from a number of different sources by the client, rather than the server. > Imagine, for example, that you have one hundred users, each able to select > from 10 or so data feeds. If you push to the client the responsibility for > getting the data, then strain is taken off your servers. But building > complex applications like that with XMLHttpRequest is very difficult -- use > XForms to capture the logic and you'll find the whole thing pretty > straightforward. It is not true that implementations in general will allow for retrieving content from arbitrary hosts. E.g. the Mozilla implementation has stated that it will only allow to retrieve and submit instances to the same host as the form it-self originated. This means that a google search where the client makes a submit directly to the google WebService API will only work if the from originated from the same host (you cannot have that form on you own server and expect it to work). The reason for having this restriction is because of security issues. This will break the use case of creating a portal directly on the client with no aggregation on the server. Best regards, David
Received on Friday, 29 April 2005 06:21:11 UTC