<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.eiffelroom.org" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>eiffelroom - web - Comments</title>
 <link>http://www.eiffelroom.org/tag/web</link>
 <description>Comments for &quot;web&quot;</description>
 <language>en</language>
<item>
 <title>Will update tutorial</title>
 <link>http://www.eiffelroom.org/article/creating_a_web_application_with_goanna#comment-374</link>
 <description>&lt;p&gt;Thanks Neal,&lt;/p&gt;

&lt;p&gt;I will integrate this info in the tutorial on Goanna&#039;s Origo page too.&lt;/p&gt;

</description>
 <pubDate>Sun, 04 Nov 2007 09:26:40 -0800</pubDate>
 <dc:creator>bayt</dc:creator>
 <guid isPermaLink="false">comment 374 at http://www.eiffelroom.org</guid>
</item>
<item>
 <title>Great Tutorial</title>
 <link>http://www.eiffelroom.org/article/creating_a_web_application_with_goanna#comment-373</link>
 <description>&lt;p&gt;Thank you for doing this, Till. One thing I&#039;d like to add is that the parameter collections are for validating the semantics of a submitted form, not for validating user input.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Mandatory Parameter Collection&lt;/strong&gt; - These are mandatory at the form processing level, not required fields in the form the user sees.  Typically, these are a html hidden elements used to verify that some system state is the same at form processing time as it was at form generation time.  For example, it might contain the user name of a logged in user to prevent them from submitting a form, logging out, logging in as a new user, and then using the back button to resubmit the previously generated form for the previous user.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Required Parameter Collection&lt;/strong&gt; - These are html elements which must be present in the form for correct processing to occur or whose absence indicates a serious bug in the form generation routine or an attack on the web site. This doesn&#039;t necessarily mean that the user must provide a value for the element. &amp;quot;address_line_2&amp;quot; on a registration page might be an example of a required parameter for which no user input would be required.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Optional Parameter Collection&lt;/strong&gt; - These are elements whose absence from a submitted form is expected sometimes. No processing for this parameter will occur if they are not present in the form.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Add If Absent Parameter Collection&lt;/strong&gt; - These are elements whose absence from a form has meaning.  html checkbox elements provide a typical example. If they are not present in the form submittal, a PARAMETER_PROCESSING_RESULT for them is added so that the appropriate processing for their unchecked state will occur.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Validating User Input&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Each GOA_REQUEST_PARAMETER is responsible for validating the input it receives from the user.  Since receiving invalid input is expected, this does not interrupt request processing. Typically, invalid user input produces&lt;/p&gt;

&lt;p&gt;&amp;quot;not PARAMETER_PROCESSING_RESULT.is_value_valid&amp;quot;&lt;/p&gt;

&lt;p&gt;which in turn triggers the redisplay of the form with an error message.  Several GOA_REQUEST_PARAMETER descendents implement this behavior for common data types.&lt;/p&gt;

</description>
 <pubDate>Sun, 04 Nov 2007 09:19:52 -0800</pubDate>
 <dc:creator>neallester</dc:creator>
 <guid isPermaLink="false">comment 373 at http://www.eiffelroom.org</guid>
</item>
<item>
 <title>Log4E</title>
 <link>http://www.eiffelroom.org/library/goanna#comment-104</link>
 <description>&lt;p&gt;This is actually a separate library, and not a cluster of goanna.&lt;/p&gt;

</description>
 <pubDate>Thu, 01 Mar 2007 10:23:10 -0800</pubDate>
 <dc:creator>colin-adams</dc:creator>
 <guid isPermaLink="false">comment 104 at http://www.eiffelroom.org</guid>
</item>
<item>
 <title>Corrections</title>
 <link>http://www.eiffelroom.org/library/goanna#comment-8</link>
 <description>&lt;p&gt;SOAP is not supported (implementation was never completed, although both Glenn and I had a go). None of the DOM stuff currently works (it was written for Gobo version 2 XML library - it should not be too difficult to fix it though, if someone wants to try). The library also includes an HTML page generation framework, based around XSLT and RELAX NG.&lt;/p&gt;

</description>
 <pubDate>Thu, 22 Feb 2007 05:27:29 -0800</pubDate>
 <dc:creator>colin-adams</dc:creator>
 <guid isPermaLink="false">comment 8 at http://www.eiffelroom.org</guid>
</item>
</channel>
</rss>
