Dan, I think that the BEST policy as far as saying Fork the Spec - would be to put any extensions and/or modifications that are not compliant with the spec into a seperate module...maybe even a seperate .jar so that they can be included but do not polutte the purity of the existing spec compliant stuff...I can give a pretty lengthy argument for this viewpoint if anyone is interested, but I'll sum it up with the folowing though... HTML had many limitations that the dominant community (web designers) were unhapy with and the speed with which the spec was modified was so slow that many vendors simply abandoned the spec and created their own implementations, which gained prominence and eventually replace the spec...consequently HTML which was originally a CONTENT based markup language became a presentation based language and thus a need for XML was born. ashley
-----Original Message----- From: Daniel Rall [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 26, 2002 8:04 AM To: [EMAIL PROTECTED] Subject: Re: Netscape browser/applet problem with SSL "Rick Johnston" <[EMAIL PROTECTED]> writes: > Very interesting. This would say to me that XMLRPC cannot be used in an > applet running in a Netscape browser with an SSL connection, since the > browser usually doesn't supply valid content-length header information > (even when the java code attempts to do so). Also, the content-type in > this configuration is as likely to be null as any other value. We had to > remove some validation code from our servlet because of this problem. Why not have the applet make the HTTP connection to the server itself (i.e. why invovle the browser at all)? > I guess this is one of the problems of working with a frozen standard. The > rest of the world doesn't necessarily care whether people can use that > standard. Yeah, I may end up forking away from the standard myself. > Just so I'm clear, can you remind me of the policy for people to modify > this type of behavior in our own implementations? Have at it (http://www.apache.org/LICENSE.txt has the details). Dan
