SignalR/SignalR — Issue #46: Signalr DateTime Request/Response disparity
Author: alangley
Created: 2011-10-25 21:54:16+00:00
State: open

I am using WCF data services to 'query' for data models from my web application, but then I use SignalR to receive 'push' updates.

WCF Data Services (OData) formats dates as a string in the format "/Date(1319493384779)/". This is fine, because I then generate client-side (javascript) viewmodels where I create actual Javascript Date() objects. SignalR also sends DateTime objects from the server to the client as "/Date(1319493384779)/", but it appears to expect an actual Date() object when passing from javascript to a server hub method via Javascript - using the above date format causes a format exception in the JSON deserializer. This is rather inefficient, because I already have a model object in javascript, and I should just be able to send it to a SignalR hub as-is.

Does anybody have any idea why this is happening?

(SO: http://stackoverflow.com/questions/7882535/signalr-datetime-request-response-disparity)