Fluent asynchronous API 1: API requirements

Posted by: More Whidbey stuff, on 05 Dec 2014 | View original | Bookmarked: 0 time(s)

Today I built a fluent asynchronous API. This is hard to do if you want the API to remain as close as possible to a synchronous API, but still maintain reliable and consistent asynchronous behavior. There are examples of this around (Erik Meijers reactive extensions come to mind), quite a few not always clear blog posts, a general functional pattern, and a few npm packages. None of this however seemed to correspond exactly to what I wanted.First, I wanted the API to look as natural as possible, surfacing...

Similar Posts

  • New Tools for Framework Designers Published more
  • Native Threading APIs in Windows Server 2008 more
  • Summary of Domain Specific Languages (DSL) meeting at ALT.NET conference - from David Diehl more
  • Streaming with LINQ to XML - Part 1 more
  • Asynchronous command execution in .NET 2.0 more
  • Why does the world need another XML API? more
  • SharePoint 2007 -- Built on ASP.NET 2.0 more
  • XSLT 2.0, Microsoft, and the future of System.Xml more
  • Project LINQ and XML - Some reflections more
  • Data Source Controls (Part 3 - Asynchronous Data Access) more

News Categories

.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Data | DataGrid | DataSet | Debugger | DotNetNuke | Events | GridView | IIS | Indigo | JavaScript | Mobile | Mono | Patterns and Practices | Performance | Podcast | Refactor | Regex | Security | Sharepoint | Silverlight | Smart Client Applications | Software | SQL | VB.NET | Visual Studio | W3 | WCF | WinFx | WPF | WSE | XAML | XLinq | XML | XSD