StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<h2>Beware - Thar be Unicorns!</h2> <p>Whenever you get optimization happy and start investigating solutions it's good to take a deep breath, list a couple of things that describe exactly what you want from both the consumer and server perspective. Be prepared to make concessions where appropriate but don't let yourself deviate too far from <strong>your requirements</strong>.</p> <h2>Well - What works for you?</h2> <p>Well - I'm glad you asked!</p> <p>I've been using the ServiceStack ...stack in production for the better part of a year. In fact it's the default provider for my iOS apps because it's just so darn versatile. Basically, you get REST + SOAP all in one implementation, and some very nice optimizations.</p> <p><a href="https://github.com/mythz/ServiceStack.Text" rel="nofollow">https://github.com/mythz/ServiceStack.Text</a></p> <p>Plus the API makes JSON really super easy. </p> <pre><code>var customer = new Customer { Name="Joe Bloggs", Age=31 }; var json = JsonSerializer.SerializeToString(customer); var fromJson = JsonSerializer.DeserializeFromString<Customer>(json); </code></pre> <h2>You wanna race?</h2> <p>[Insert gratuitous 2 Fast 2 Furious joke here...]</p> <p>Well yes indeed. I'm a huge fan of Demis Bellot [mythz] and his work, <strong>in fact</strong> he's working at StackOverflow now. Sufficing to say, he's a perf & optimization nut, so if something is slow, you're almost certain it's not <em>his</em> code that's the issue :-P</p> <p>Here's some benchmarks to wet your beak:</p> <p><a href="http://www.servicestack.net/mythz_blog/?p=344" rel="nofollow">http://www.servicestack.net/mythz_blog/?p=344</a></p> <p><a href="http://daniel.wertheim.se/2011/02/07/json-net-vs-servicestack/" rel="nofollow">http://daniel.wertheim.se/2011/02/07/json-net-vs-servicestack/</a></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