Microsoft Socket API and Microsoft potential Sysapps recommendations support

Hi,

Note: This discussion is not limited to the Socket API.

It is probably because we have no participant from Microsoft, but I worry a little on that we didn't do much consideration to their Windows 8 Socket APIs which are shared among 4 languages (JavaScript, C#, C++, and VB)
-> Windows.Networking.Sockets: http://msdn.microsoft.com/en-us/library/windows/apps/windows.networking.sockets.aspx


Fact is that these JavaScript available APIs doesn't seem to consider that much W3C API design neither. Their WebSocket API doesn't really look compliant with the W3C one.
-> http://msdn.microsoft.com/en-us/library/windows/apps/windows.networking.sockets.messagewebsocket.aspx



As a newbie in W3C processes and internal "negotiations" I wonder:

        • Are there been some attempts to get Microsoft representatives in the working group? More globally, is it traditionally part of the working group creation to try to get representative of each major implementers?

        • How much should existing JS API implementations, like those previously mentioned, impact the work for the W3C standards version to encourage their future migration?


Part of my worries are motivated by how much I'd want Web Developers to be able to use Sysapps APIs for Windows apps as for other ones. But of course we should still have the possibility to use polyfills, so that's not a full dead-end/cul-de-sac ;-)

Alexandre.




Alexandre Morgaut
Wakanda Community Manager

4D SAS
60, rue d'Alsace
92110 Clichy
France

Standard : +33 1 40 87 92 00
Email :    Alexandre.Morgaut@4d.com
Web :      www.4D.com

Received on Tuesday, 12 November 2013 09:41:33 UTC