Hi tarlano -
I will have to give it a shot. It might be a case of the http versus tcp port choice (http.sys). I have not tried what you are talking about, but I would be interested in seeing if it didn't work. Thanks!
Comments
-
-
Not a bad idea... I have some other things I want to show there as well. Hmm...
For your immediate relief, have you seen the WCF on Azure samples and troubleshooting guidance?
http://code.msdn.microsoft.com/wcfazure
Check the Known Issues link there and see about a few gotchas due to the load balancer and the QFE hotfix (already in cloud, btw).
-
Hi Hansol -
Sorry to hear about your issue. Take a look at episode 2 I think where the TotW is how to troubleshoot that problem. Here is the link that we refer to:
Steve and I also did a video called 'Hello Windows Azure' that might be the walkthru you are looking for.
http://channel9.msdn.com/posts/dunnry/Hello-Windows-Azure/
If you have idea for other topics you would like to see, leave us a comment or use @cloudcovershow and share your idea. Thanks for watching!
-
The whole issue with concurrency is to make sure that only one instance is processing the work. The 'golden ticket' approach does not apply to work that can be done in parallel. You would only use that approach when you wanted to ensure that something was done once and only once in an otherwise parallel environment. Make sense?
-
@jigneshpandya - In general, you don't set limits. That is, you have some limits like 100TB of total storage (blobs, tables, queues) per storage account (up to 5 accounts by default). Are you asking something else?
-
Hey Shane, you're right... the video stops playing when hitting full screen. I will have someone look into it. Thanks!
