{"id":1621,"date":"2012-02-23T08:36:55","date_gmt":"2012-02-23T07:36:55","guid":{"rendered":"http:\/\/www.pleus.net\/blog\/?p=1621"},"modified":"2012-02-23T08:40:16","modified_gmt":"2012-02-23T07:40:16","slug":"ria-goes-to-hollywood","status":"publish","type":"post","link":"https:\/\/www.pleus.net\/blog\/?p=1621","title":{"rendered":"RIA goes to Hollywood"},"content":{"rendered":"

Most RIA technologies today use an asynchronous model to communicate with the server, primarily to keep the UI responsive no matter what the server is doing. This principle is also known as the Hollywood principle<\/a>. Don’t call us, we call you<\/em> means that instead of continuously polling, the server calls back when the operation finished. In order to be notified when the server finished its job, callbacks are used. <\/p>\n

For instance in Silverlight this leads to code like this<\/p>\n

\r\nvoid ClickLoad()\r\n{\r\n    LoadCustomer(1,\r\n    (result) =>\r\n    {\r\n        \/\/ Process result\r\n    },\r\n    (error) =>\r\n    {\r\n        \/\/ Process error\r\n    });\r\n}\r\n\r\nvoid LoadCustomer(int id, Action<Customer> success, Action<Exception> error)\r\n{\r\n    LoadFromServer(\"select * from customers where id = \" + id,\r\n    (result) =>\r\n    {\r\n        success(result[0] as Customer);\r\n    },\r\n    (exp) =>\r\n    {\r\n         error(exp);\r\n    });\r\n}\r\n\r\nvoid LoadFromServer(string query, Action<List<object>> success, Action<Exception> error)\r\n{\r\n    server.LoadCompleted += (s, e) =>\r\n    {\r\n        if (e.Error != null)\r\n            error(e.Error);\r\n        else\r\n            success(e.Data);\r\n    };\r\n\r\n    server.LoadAsync(query);\r\n}\r\n<\/pre>\n
Not very nice, is it? In jquery we find a similar pattern.<\/p>\n
\r\n$.ajax({\r\n  url: 'ajax\/load.html',\r\n  data: \"query=1\"\r\n  success: function(result) {\r\n    \/\/ Process result\r\n  }\r\n  error: function(XMLHttpRequest, textStatus, errorThrown) {\r\n    \/\/ Process error\r\n  }\r\n});\r\n<\/pre>\n
Usually an application consists of several layers. In that case the callbacks have to be routed back to the original caller, leading to code that is neither easy to read nor easy to maintain.<\/p>\n
From what is already visible<\/a>, it is very likely that Silverlight and WinRT are going to have great overlap. The combination of XAML, C# and WinRT plus the tooling will be very familiar to all Silverlight users.
\nThat means, it is likely that the asynchronous programming model will be the predominant model for client\/server communication for Windows Metro style apps. In order to simplify this, C#5.0 is going to include the await\/async<\/strong> keywords, that will make callback chaining obsolete.<\/p>\n
Example:<\/p>\n
\r\n\r\nvoid ClickLoad()\r\n{\r\n    try\r\n    {\r\n        Customer result = await LoadCustomer(1);\r\n        \/\/ Process result\r\n    }\r\n    catch(Exception e)\r\n    {\r\n        \/\/ Process error\r\n    }\r\n}\r\n\r\nasync Task<Customer> LoadCustomer(int id)\r\n{\r\n    List<object> result = await LoadFromServer(\"select * from customers where id = \" + id);\r\n    return result[0] as Customer;\r\n}\r\n\r\nasync Task<List<object>> LoadFromServer(string query)\r\n{\r\n    return await server.LoadAsync(query);\r\n}\r\n<\/pre>\n
This is much cleaner than the examples above. Actually it is a synchronous programming model supporting an asynchronous runtime model. As asynchronous calls are very common in RIA applications the async\/await<\/strong> keywords are going to change the way we program async calls in the near future, leading to code that is easier to develop and maintain.<\/p>\n
I can’t await async in C# 5.0 \ud83d\ude09<\/p>\n","protected":false},"excerpt":{"rendered":"
Most RIA technologies today use an asynchronous model to communicate with the server, primarily to keep the UI responsive no matter what the server is doing. This principle is also known as the Hollywood principle. Don’t call us, we call you means that instead of continuously polling, the server calls back when the operation finished. … Continue reading RIA goes to Hollywood<\/span><\/a><\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,12],"tags":[35,81],"class_list":["post-1621","post","type-post","status-publish","format-standard","hentry","category-ria","category-silverlight","tag-csharp","tag-ria"],"_links":{"self":[{"href":"https:\/\/www.pleus.net\/blog\/index.php?rest_route=\/wp\/v2\/posts\/1621","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.pleus.net\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.pleus.net\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.pleus.net\/blog\/index.php?rest_route=\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.pleus.net\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1621"}],"version-history":[{"count":69,"href":"https:\/\/www.pleus.net\/blog\/index.php?rest_route=\/wp\/v2\/posts\/1621\/revisions"}],"predecessor-version":[{"id":1691,"href":"https:\/\/www.pleus.net\/blog\/index.php?rest_route=\/wp\/v2\/posts\/1621\/revisions\/1691"}],"wp:attachment":[{"href":"https:\/\/www.pleus.net\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1621"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.pleus.net\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1621"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.pleus.net\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1621"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}