@PeterF: For inbound email it definitely could work. For outbound it matters that the sending mail server's IP address is the proper IP address(es) for the sender's email domain. i.e. an email from dave@example.com should show in the headers that it originated from example's email server; otherwise, it will get rated negatively as spam. The article didn't go into detail about the outbound side.
Discussions
-
-
For me, watching any of the short videos via HTML or Silverlight is always fuzzy. The video is not long enough for the full screen silverlight bit rate adjustment to occur. The HTML blown up to 400% isn't any better either.
Here is an example:
Got any tricks to share for helping the server crank up the bit rate quicker?
-
@wkempf: What about a daily video log starting today through the 90th day at work? Of course it would be 5 years before it could be released. doh! However, 5 years from now it would make an interesting look back at how Sven's hair turned gray.
-
Happy Birthday to you. Happy Birthday to you. Happy Birthday dear var nameeeeeeeee. Happy Birthday to you.
-
@GoddersUK: It wasn't just you.
-
Top menus now drop down on touch screen - nice. Tapping Forums for example allows for selecting coffeehouse without having to wait for another screen and then finding coffeehouse on that and then clicking.
-
8 hours ago, RetroRecursion wrote
*snip* we tried using just the simple file storage to post some files *snip*
Interesting ... By simple file storage do you mean blob storage? Something like this azure sample doesn't work beyond 100 MB?
-
@PopeDai: Thanks but you don't have to. I posted on the Azure forums to see what others might be seeing (if they care to share).
-
@figuerres: SQL Azure has its own replication strategy to ensure no data loss but when it comes to making a backup at a certain point in time it does not have that capability like we would do in SQL Server. So say your user is about to perform a significant function in your system and you would typically auto-generate a backup prior to this operation for the user's safety as an example. In SQL Azure you have to make a copy of the database then bacpac export that copy to Azure storage. The reason you have to make a copy of the database is because SQL Azure provides a transactionally consistent set of data in the database copy that you would not get if making a bacpac directly from the live database.
EDIT: worth a mention, the exporting of the bacpac of that 2.7 GB database to Azure storage took 1 Hour and 13 minutes on top of the 25 minutes waiting for the database copy. (important detail: all in the same datacenter)
-
I'm curious if anyone would like to share their good or bad Azure experiences. We've just recently decided to back away from SQL Azure for a bit. We seem to spend a lot of time working around issues or fabricating new ways to do things that just work under SQL Server. The killer this past week was a fairly reasonable database size (2.7 GB) taking 25 minutes to copy to a new database on the same server as the source database. In and of itself it wouldn't have been the trigger to back away. However, since there isn't a backup mechanism in SQL Azure and this is why the database copy strategy is suggested ... that kinda helped a lot.
The tooling in Visual Studio helps a lot. Creating web roles, worker roles, packaging it up, all good. It is difficult at times to see the differences in the projects for azure versus on-premise. I'd guess for someone who already knows Azure differences it makes sense. For me going the other way, from VS to discovering Azure differences, it is't always readily transparent. Nothing bad. I often just have that unsettled feeling that there is more going on under the covers that I really need to know about to really understand .... and leverage.
Azure's auto load balancing with inrole shared caching rocks in concept. We need to progress further along with Azure to see how it performs though.
I'm bummed and was just curious to hear from others.
