- From: Arthur Barstow <art.barstow@nokia.com>
- Date: Tue, 28 Feb 2012 11:43:40 -0500
- To: "ext Michael[tm] Smith" <mike@w3.org>
- CC: "public-webapps-testsuite@w3.org" <public-webapps-testsuite@w3.org>, Kris Krueger <krisk@microsoft.com>
On 2/27/12 11:26 PM, ext Michael[tm] Smith wrote: > Hi Art, > > I wasn't actually proposing anything. I certainly didn't mean to suggest we > should restrict everybody to only writing WebSocket server pieces in > Python. My purpose was just to let everybody know that it's now possible to > write WebSocket server parts in Python and run them on w3c-test.org. And > now that we have Jetty set up, it's also possible write tests in Java and > run them there too. > > As I said in the other message I just now sent to you and Kris, I think we > can support multiple formats on the server side -- within reason of course. > I don't want to end up installing some obscure system just because somebody > prefers to write tests using it. But I know already that multiple browser > projects are using pywebsocket for testing internally, and I know that > Jetty in general is widely used too, so it's worthwhile to have Jetty > available as well for anybody who wants to use it. Thanks for the clarification Mike (it seems reasonable to me to support more than one format for the server). -AB > --Mike > > Arthur Barstow<art.barstow@nokia.com>, 2012-02-27 14:12 -0500: > >> [I just realized this email did not go to WebApps' testsuite list] >> >> Mike, Kris, All - how does Mike's proposal below compare to the proposal >> Kris made last week: >> >> http://lists.w3.org/Archives/Public/public-webapps-testsuite/2012Feb/0014.html >> >> >> -Thanks, Art
Received on Tuesday, 28 February 2012 16:44:10 UTC