SyncReply removed, not backwards compatible?

[Cyle Witruk]

Hi,

We're in the process of upgrading to v4 and noticed that the default "SyncReply" route was removed in favor of "Reply".  We have customers who are actively using these URL's in our services.  What is the recommended way to achieve backwards compatibility for these customers, without having to manually register the routes for each content-type+service?

Cheers,

Cyle

[Cyle Witruk]

Moved this to stackoverflow: http://stackoverflow.com/questions/21534493/servicestack-syncreply-removed-not-backwards-compatible