Smartforms experience...

We have seen major differences in the GUI response to a user event based on the size of the XML which is bounded to a Smartforms form / page.

The form we use doesn't have many controls on it (approximately 6 or so). When we trim the XML document to only contain the elements which are mapped to the form, we see significant reductions in the GUI event response time. Basically, delays are no longer noticeable.  In our case we trimmed the XML document from 726 KB to 1 KB and the response time improved dramatically. Even when we trimmed it down to 222 KB and 91 KB, we still saw delays.

We are working with Blaze support to see if they can recreate the problem and then analyze further.

Regarding your implementation, I am interested in understanding how you are planning to deploy.  Whether or not it is a separate web application and if so, how do you secure the application. One of the concerns we have is with two separate web applications. The main web application will interface with the Smartforms component  in a separate web application and displayed in an IFRAME. We will use a url with IFRAME tags for the Smartforms component.   As far as we know there isn't a way to secure the Smartforms web application.  If anyone knows what the URL is, they can access the Smartforms web application. 

An ideal way to go is to have the Smartforms component as a portlet within a portal.  But since this is an existing application, there is not any interest at this time to redesign and implement into a Portal.  Any ideas you can share are appreciated.

Thanks,

Joe Garrity