Their company sells $100m worth of software a year in 130 countries around the world, but has no sales staff. Now Atlassian – a billion-dollar business built by two Sydney friends in an apartment and then an office above a sex shop 10 years ago – is widely tipped to be the first Australian tech startup to go public during the current boom. (via The boys who built a $1b company in the cloud)
Single parameters work fine in either of these RPC scenarios and that’s to be expected. ModelBinding always works against a single object because it maps a model. But what happens when you want to pass multiple parameters?
Consider an API Controller method that has a signature like the following:
public string PostAlbum(Album album, string userToken)
Here I am asking to pass two objects to an RPC method. Is that possible? This used to be fairly straight forward either with WCF REST and ASP.NET AJAX ASMX services, but as far as I can tell this is not directly possible using a POST operation with WebAPI.
A few times after tweeting about Noda Time, people have asked why they should use Noda Time – they believe that the .NET date and time support is already good enough. Now obviously I haven’t seen their code, but I suspect that pretty much any code base doing any work with dates and times will be clearer using Noda Time – and quite possibly more correct, due to the way that Noda Time forces you into making some decisions which are murky in .NET. This post is about the shortcomings of the .NET date and time API. Obviously I’m biased, and I hope this post isn’t seen as disrespectful to the BCL team – aside from anything else, they work under a different set of constraints regarding COM interop etc.
Using HTML entities is the right way to ensure all the characters on your page are validated. However, often finding the right entity code requires scanning through 250 rows of characters.