Fields are to ease input validation, and don't apply to transport
mechanisms at all. WAP applications send plain old html to browsers,
not objects. Fields are a better way of building web applications,
not a new transport protocol for driving browsers.
For background tune into http://virtualschool.edu/wap
>>Then look at where JSP deals with field request parameters. You'll
>>find that request->getParameter() returns Strings/nulls, which is the
>>point of my complaint that "Fields are not Strings". JSP provides no
>>tools for treating field parameters as application specific field
>>types. I explained why this was bad and how to fix it. Even provided
>>an AbstractField class that you're free to use if you want even
>>within JSP.
>
>Again, I don't have that much of a problem with this. I *do* see it as a
>slight limitation of the transport mechanism, because sending objects that
>aren't identifiable isn't an easy or clear thing when you only have 8 bits
>to work with (and yes, I know I'm ignoring UNICODE.)
--
---
For industrial age goods there were checks and credit cards.
For everything else there is mybank.dom at http://virtualschool.edu/mybank
Brad Cox, PhD; [EMAIL PROTECTED] 703 361 4751
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
