Toluu : Tales from a Trading Desk

Tales from a Trading Desk

Noise from an Investment Bank

I was planning to try deploying the DistributedSort example into Azure tonight, but failed at the first hurdle when I realised I had no Hosting service account - I have the .NET services. Hopefully one will turn up soon.

I’ve got the EchoService sample running (I had an out of date CTP ). I’m not curious if I could pump prices up to the cloud and get Silverlight clients to receive them in a timely fashion. Anyone got any Service Bus performance figures? The EchoService uses netTcpRelayBinding, but I want COMET?. Microsoft.ServiceBus assemble is also not Silverlight compatible Anyone at Microsoft care to comment?

Since I can only deploy a WF via XOML, to get an RFQ/S workflow working and put the limit/credit checking into the cloud I’d need to deploy C# logic into a WebRole or

Azure: Microsoft .NET Services and Microsoft SQL Services Invitation CodeYesterday

I finally got round to requesting and invitation a few days ago. Tonight I got the invitation code

Azure Invite

Trying to run the Echo service bus example was going too well, the service started fine, but the client failed with the following Looks like other people have had issues as well.

The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.

WF RFQ/RFS Negotiation ThoughtsJanuary 5

I’ve missed reading the last three issues of MSDN Magazine, so this morning I printed the interesting articles to read for my daily commute:

Cloud Gazing From Silverlight 2
Browser Interoperability In Silverlight 2
Silverlight 2 Transforms And Clipping Regions
Best Practices For Windows Workflow Foundation Apps
Render Text On A Path With WPF
Thread Management In The CLR
WCF And WF Services In The .NET Framework 4.0 And “Dublin”
When Things Go Wrong
An Introduction To RESTful Services With WCF
Managing Dynamic Content Delivery In Silverlight, Part 1
Round-Robin Acce

Silverlight Business Applications Across Networks - ThoughtsDecember 31 2008

Bruce posts on the ISV Developer Community blog about the January 2009 MSDN Magazine article “Build Line-Of-Business Enterprise Apps With Silverlight”. The article is definately worth a read. I’m unfortunately left with the question of why from Hanu’s perspective I have to do Push notifications using “Silverlight only allows the connections to the server ports in the range of 4502 to 4532″ and “runtime will make a connection to an IP endpoint on the same IP address with the port number 943. This port number is hardwired to the Silverlight implementation and can’t be configured by applications or changed by the application developer”. If I deploy my Silverlight Push RIA to thousands of client all running within different corporations that have strict firewall security (which by default allow port 80/443 access), will I have to submit n pieces of paperwork to n corporations to get the 45xx port open to my external server for push to work?

Further Azure ThoughtsDecember 29 2008

The Azure SDK comes with a number of samples including the default Hello and the more interesting Distributed Sort sample.

The Distributed Sort is interesting since it provides an easy to follow example of an ASP.NET front end connecting to the work item (Azure service) via a queue (persistent messaging between services). AJAX is used to provide the “real-time” update on the web page. The sample itself is configured to use only one worker role instance, but changing the .cscfg file allows more workers to be created - when I run on my local Development Fabric I’m only running across my two CPU cores, how do the Worker’s get distributed in the Azure Services Developer Portal?

Fabric services need one or more roles:

A web role is a web application accessible via an HTTP and/or an HTTPS endpoint. A web role is hosted in an environment designed to support a subset of ASP.NET and Windows Communication Foundation technologies.
A worker role is a background processing application. A worker role may communicate with storage services and with other Internet-based services. It does not expose any external endpoints. A worker role can read requests from a queue defined in the Queue storage service.

One question I have is around the .NET Service Bus