> The portlet spec is locking out client-side technologies!! If the > arguments and points that I have presented have not convinced you > then sobeit.
I am not saying that the current spec does or does not lock out client-side technologies. I for one would rather say that it carefully avoids mentioning them. Some posters in this thread have started to suggest that maybe you can use some client-side technologies while still following 168. I don't know if that is realistic or not.
What I am saying though is that the world of client-side is complex and unevenly supported by clients, I am suggesting that you make more concrete suggestions as to how a portlet specification could support them better than 168 does. Theory vs. practice, if you will.
> I can pretty much guarantee you that going forward with the spec the > way it is it will fail.
Wanna bet money? ;-)
-Erik
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
