Are WCF Data Services dead for Silverlight? -


wcf ria services got updated few days ago. wcf ria services got complex objects, tt templating, etc.

wcf ria services have (by default) fast , compact binary transport. wcf data services have bloated xml atompub format.

is microsoft abandoning wcf data services silverlight in favor of wcf ria services?

personally, wcf data services more, because of simplicity, openness, cross-platform, , normal (on demand) proxy (re)generation (wcf ria services regenerate proxies every time build, leads recompilation of silverlight project, leads new xap packaging , redeployment, usability killer).

will ever see support of xml-msbin format wcf data services?

will ever possible use non-microsoft datacontext, not wrap nullable fields in clause, making sql bloat, ugly , slow?

those issues make me feel, wcf data services have no more priority...

i don't think wcf ria services should confused odata or wcf data services. data services/odata options should considered based on need. if have silverlight application not exposing data of partner or third party doesn't make sense go wcf data services. instead better off wcf ria services because of richness provides. whereas looking application not caters , intranet or internet plus expose data platform neutral way - that's when need think odata instead of wcf ria.

in short odata breaking data silos , exposing data in platform independent way. java, php, obj-c, etc., etc., know how consume odata because of standard xml + atom/atompub format.

hope made point clear :)


Comments

Popular posts from this blog

Add email recipient to all new Trac tickets -

400 Bad Request on Apache/PHP AddHandler wrapper -

php - Change action and image src url's with jQuery -