StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>After some thought, reading your replies (and some others on msdn forums) and analysing my scenario, the query patterns and the technologies I'm more comfortable with, I decided on the following:</p> <p>A unified Web Api model over SQL Azure (it might even return an OData IQueryable in one case) will handle both message sending and matchmaking. </p> <p>Message forwarding to the windows 8 hub app will be done through SignalR and Web Sockets. These two links show me how to handle the app going to the background ( <a href="http://msdn.microsoft.com/nl-be/windows/apps/jj662740.aspx" rel="nofollow">http://msdn.microsoft.com/nl-be/windows/apps/jj662740.aspx</a> ) or losing connectivity (<a href="http://msdn.microsoft.com/nl-be/windows/apps/jj710180" rel="nofollow">http://msdn.microsoft.com/nl-be/windows/apps/jj710180</a>) - still I want to support some minutes of lost connectivity during which the server will accumulate the messages and send all those that have not been received (after a time period the match will be considered over and the database will be cleaned - I am not sure if I'll handle this programmatically or with a Workflow on a Worker Thread. At this point it seems simple enough to handle programmatically).</p> <p>In case I need push notifications during matchmaking, I can implement them in Web Api (it takes a few more work than in Mobile Services): <a href="http://www.codeproject.com/Articles/506733/Windows-8-Notifications-Push-Notifications-via-Win" rel="nofollow">http://www.codeproject.com/Articles/506733/Windows-8-Notifications-Push-Notifications-via-Win</a></p> <p>So it's more like the solution 2. I'll keep you posted if I encounter any complications. I might need a bit more code initially to set this up over Mobile Services, but I think I will be able to expand the solution in a more seamless way once I follow the basic tutorials to set up the basics. I might even try Entity Framework 6, to go all-async and minimize throughput overheads over node.js (but I'm not expecting any serious load anyway).</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload