• Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

Comments (2)

1 eFormsAdvocate commented Permalink

Interesting blog entry; from my interpretation I read this as saying that the support of the xfdl format elements is to become deprecated or even unsupported in the log term. Previously I have been under the impression that large forms have better performance if the number of XForm binds is limited, are you able to confirm that large forms with large numbers of binds will perform better than the xfdl equivalents?. <div>&nbsp;</div> Also is this shift in approach relevant to Forms v4 or Forms R-Next?.

2 John M. Boyer commented Permalink

A colleague and I recently worked on a form that had nearly 500 XFDL formats of the types described in this blog entry, and I converted them to XForms binds. During client-technology execution (Webform server and Viewer), we found there was some advantage, though not huge, in using the XForms binds. This was both in terms of run-time performance and memory footprint. <br /> However, the big benefit realizable in the current product has to do with use of "on demand page loading". When the data validation constraints are built into gthe XFDL presentation layer, it means that the XFDL presentation layer has to be fully articulated in order to perform the data validation checks. By comparison, if the XForms binds are used, then validity of an XForms submission of the data is not dependent on loading pages. When users perform a fill experience over multiple sessions, or perform updates of previously completed forms, this can make a huge difference in the cost of completing the incremental update of the form. <br /> As for LF4, there's more interesting stuff to say, but I'll have to revisit this topic once LF4 actually ships. <br /> Finally, as for deprecation of the format option, I'd say mainly that the format option is really about formatting information, and the constraint validation capabilities were included in it way back when there was no separately articulated data model. But we've been shipping XForms capabilities for about five years now, so it's time to at least delegate, if not deprecate, the data validation capabilities of XFDL format in favor of those available in XForms. Generally speaking, we like to let XForms do what it does, and then let XFDL add more business value on top of that.

Add a Comment Add a Comment