-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Apr 11, 2009, at 3:29 PM, Alan Burlison wrote: > > We've discussed this in the past on this list: > > http://www.mail-archive.com/[email protected]/msg00032.html I went back and read that thread. Here's what I found: 1. A weak defense of the Stripes assumption. 2. Exhale: A defense for XHTML, Inhale: mime/type amnesia 3. A bunch of blather about "tag soup" that is old as IE 6. The argument makes no consideration for browser modes: Quirks and Standards. Any web tier developer worth their salt knows exactly what these modes are and what they do. "Tag soup" is less of a valid argument in the context of today's clients, where *well-formed and validated* HTML 4.01 is not "tag soup". I don't believe this is a "partisan" position. It is a specification position. And the XHTML assumption is, in IMHO, a barrier to both ease- of-adoption and acceptance. A response that returns " />" (space+solidus+gt) *assumes* that the web tier developer is going to code to a XHTML DTD. Nothing more. Nothing less. It is an assumption that Stripes should not be making. How Stripes got here is a cocktail of "nerd angst," concern about just how to handle it in the library, and a good faith effort by Stripes developers. My original thought was to overload writeSingletonTag or have another method ("yet unnamed"), to branch the output to the response. In reading the code more, I've decided that it is much *simpler* than that, and actually allows Stripes to retain some of its assumptions. writeSingletonTag will examine the mime/type. If either "application/ xhtml+xml" or "text/xml" it will work as currently designed, returning " />". Anything else, i.e., "text/html", the response will properly return ">", per the HTML 4.01 DTD and Specification. This way Stripes remains a vanguard in the community by promoting best practices. *However* I don't think the above fix can get away without a deprecation warning. Reason: too many Stripes users may have adopted writing invalid HTML 4.01 to an XHTML DTD. You have to maintain this confused community for a bit. Thus, and still a simple solution, introduction of a context-param that initializes the use of HTML/ XHTML, and branch in writeSingletonTag appropriately. I will want to discuss this with the Stripes Developer list, as I will likely do this in a local JAR build (and contribute a patch). I need to understand where the context is bootstrap'd and appropriately use the param in writeSingletonTag. Bottomline, if Stripes assumes anything, XHTML content will be using the correct mime/type. Regards, Tim -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Ask me how you can start digitally signing your email! iEYEARECAAYFAknlQVIACgkQNsfkZJstizrvVwCeIeeVFYNhwxL0zRVSux298NQh eeQAn3FCPLU+LmqO5hDHyVPFsYMLwad6 =r3Mb -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Stripes-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-development
