On Tue, Oct 28, 2008 at 6:32 PM, Jim Washington <[EMAIL PROTECTED]> wrote: > > A bit of history on this. The content-type in this bit of code was > determined more than three years ago by testing with several old major > web browsers. At the time, 'application/x-javascript' was the > content-type that reliably told the web browser to use its javascript > parser on the document so that the rpc data could be used. Other > settings did not work on all of the web browsers I tested. > > So, this content-type was decided empirically (a long time ago), not > from specification. It maybe should continue to be the default for > compatibility with creaky old web browsers. But maybe it can be > changeable (if you *really* know what you are doing) so that the > outgoing document can meet the expectations of client libraries. > > - Jim Washington > >
Reasonable. Then it would be nice to add a configuration directive so that user can set the content-type based on the requirement of client libraries. For me, I am using IE6, IE7, FF2 and FF3 with the ExtJS library and applicatin/json works fine. -- Hong Yuan 大管家网上建材超市 装修装潢建材一站式购物 http://www.homemaster.cn _______________________________________________ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users