With the new release of WebSync, developing from your local machine (a.k.a. localhost) is easier than ever.

Instead of using special "reserved" keys for localhost, go ahead and use your regular domain key. The rest is taken care of behind-the-scenes.

For the JavaScript client, just specify your domain key. For the .NET and PHP clients/publishers, specify your domain as well (without http://, port numbers, or sub-folders, as usual, e.g. frozenmountain.com).

Update

An option has been added to the Portal which allows you to disable this feature per-domain. Simply uncheck "Allow communication from localhost"."

We are pleased to announce that after many internal revisions and much hard work, version 2.3 of WebSync Server and WebSync On-Demand has been released. The list of changes is extensive. Here are the highlights:

• Server performance has been improved. We have tested over 30,000 actively communicating clients on a single channel on a single server.
• Reorganized and updated documentation. It should be more intuitive to navigate and understand. (No more synchronous/asynchronous tech-speak.)
• .NET and PHP proxy support for pre-processing client requests. Allows custom server-side application logic. Check out the documentation for more details.
• Support for extra data in messages. Authentication and other security features should be easier to implement now if sessions are not available.
• Improved JavaScript support. Browser support is very extensive, going back to earlier revisions further than we can test. Browsers will automatically take advantage of new HTML5 features for improved performance as they become available.
• Enhanced .NET and PHP core downloads. Clients and publishers should see faster communication.

A very big thanks to all the feedback we have received, both positive and negative. You are the most important part of this, and we are always listening to what you have to say.

A Visual Studio plug-in is on the way for WebSync Server customers. Watch for it!