I know a city building inspector who wants to be able to see the building design as an overlay on the actual job site. If Microsoft wants to do a trade of development for them in exchange for promo material I can get you some contacts. It isn't as fancy as NASA but come on, its more tangible to a wider audience.
The settings of the webrole in the portal would be better if your service will only be housed in a web role.
Seems like we tried that route and bailed because the same service needed also be self-hosted. ...and that led to compile complexities because there was not azure refs in the self-hosted parent. Although that history is really fuzzy right now.
@figuerres: ah. that refreshed some memory. we saw that as well and went to use SlowCheetah for the transforms. then something was going wonky with the SlowCheetah package in VS.
That has been a while and it appears to have new bits since.
@figuerres: In the WebRole we tried using a transform over the web.config to hold the setting. So we had a Web.Debug.Config, a Web.Release.Config, and of course the Web.Config that gets rolled into. The transform part wasn't always working or gave problems so we dropped using transforms and just xcopy the proper config.
If you are using azure websites ... I dunno. Haven't gone there yet.
In the beginning there was only one path and that was the cloud service. Later came the web site jobs (for a lot of the logic you describe from what I recall).
Last time I opened an HDD (last week), the mechanism still used a magnet on the armature to flip the bits. I'm pretty sure a speaker magnet stuck to the platters will wipe it. So I'm with John on this one.
I wonder if they have a magnetic field map that shows the layout of the magnetic field in relation to the component layout within the case?
At some point of miniaturization, it seems like a nudge from a magnetic field would cause some sort of interference with an electron moving between points.
I'll do some more digging on this to find out if the "Internet" definition is inclusive of the TCP/IP protocol running across the network. If it is then I stand corrected as the TCP/IP protocol is what does the retries. When I wrote the comment I was under the assumption the "Internet" was an Ethernet network (which doesn't necessarily specify the protocols running on top).
Addition: Yep. Internet protocol suite does specify TCP/IP. http://en.wikipedia.org/wiki/Internet_protocol_suite
"The layers of the protocol suite near the top are logically closer to the user application, while those near the bottom are logically closer to the physical transmission of the data. Viewing layers as providing or consuming a service is a method of abstraction to isolate upper layer protocols from the details of transmitting bits over, for example, Ethernet and collision detection, while the lower layers avoid having to know the details of each and every application and its protocol."
Thanks Toast. I hadn't realized it was restricted in this way.
Okay. After some more reading it does look like the stack stops as IP. Thanks Figs. I was thinking I just got old or something.
"The Internet layer has the task of exchanging datagrams across network boundaries. It provides a uniform networking interface that hides the actual topology (layout) of the underlying network connections. It is therefore also referred to as the layer that establishes internetworking, indeed, it defines and establishes the Internet. This layer defines the addressing and routing structures used for the TCP/IP protocol suite. The primary protocol in this scope is the Internet Protocol, which defines IP addresses. Its function in routing is to transport datagrams to the next IP router that has the connectivity to a network closer to the final data destination."
"IP is not designed to be reliable and is a best effort delivery protocol. This means that all transport layer implementations must choose whether or how to provide reliability. UDP provides data integrity via a checksum but does not guarantee delivery; TCP provides both data integrity and delivery guarantee by retransmitting until the receiver acknowledges the reception of the packet."