Nicola Ken Barozzi wrote:
> Not necessarily. If you look at the W3C site, the XForms proposal, you will see
> that they want to send XML directly to the server, no parameters.
> When you want to send an array of data the size of which is not known beforehand,
> with normal forms you must send a parameter with the elements divided by some
> character and parse the string in the server.
> With XML, you just send XML, no need to reparse yourself.
What kind of market is there for the browsers that sends XForms?? Currently and in the
next 6 months.
> And the 'processor' of the form doesn't
> create the response, it just transforms the form into the valid xml posted
> by the client for further processing.
> I want to make it as modular as possible.
Ok, what you are saying is basically,
There is a XFormGenerator, that takes the request and streams the SAX events from the
posted XML.
Any processing of the posted data is done as a "Transformer" (formerly a Filter), with
possible "side effects" such as updating a database, and otherwise streamed down the
line in a normal fashion.
I buy that. Clean.
A possibility would then be that the "Validation" stage would be in the Pipeline as a
Chooser, which then direct the processing according to validation of fields.
Niclas