Microsoft Hailstorm
-
Ok guys time to fess up what you know, let's see if we can get some juice on this. On Monday MS is set to announce the scope and breadth of the next version of Microsoft Instant Messenger, codenamed Hailstorm. Thing is that the rumor mill has Hailstorm including everything from on-line web storage, to software components, to an advanced peer to peer distributed computing architecture (the routing, cataloging, and transaction engine for SOAP) and more. The general consensus is that Microsoft basically cloned Jabber wholesale and used it as the foundation for Microsoft's web services delivery system. Dave Winer, of UserLand (and contributor to the SOAP spec) had this to say after attending an invite-only NDA event in Redmond: If you're a reporter and thinking you know what they're going to talk about on Monday, trust me, you don't. Go, and listen, and think. Their plan is as big as the D-Day announcement they made in 1995. It's good fodder for the software industry, it should wake a lot of people up, and open up some closed boxes, which is a good thing. Dann Sheridan had this to say after a concept meeting held last summer: In addition to the brief diagram they drew, we discussed the specific types of services that would be offered. Here are the categories -- application, library, transactional, and utilities. Application services would include things like Office, Great Plains, Visio, etc. Library services would include access to advanced C# libraries like those produced by Dundas, advanced ASP+ components, and other high value functionality for developer to embed in their applications. Transactional services would include payments, purchases, settlements, funds transfers, etc. Utility services would include things like back-up and restore services, disk watchers, all types of system monitoring, etc. You can't do this stuff without some kind of router. Feel like a Hailstorm yet? You better believe it. Sounds like the stage is set for a major reshaping of our entire world. Anybody with deeper knowledge care to comment?
-
Ok guys time to fess up what you know, let's see if we can get some juice on this. On Monday MS is set to announce the scope and breadth of the next version of Microsoft Instant Messenger, codenamed Hailstorm. Thing is that the rumor mill has Hailstorm including everything from on-line web storage, to software components, to an advanced peer to peer distributed computing architecture (the routing, cataloging, and transaction engine for SOAP) and more. The general consensus is that Microsoft basically cloned Jabber wholesale and used it as the foundation for Microsoft's web services delivery system. Dave Winer, of UserLand (and contributor to the SOAP spec) had this to say after attending an invite-only NDA event in Redmond: If you're a reporter and thinking you know what they're going to talk about on Monday, trust me, you don't. Go, and listen, and think. Their plan is as big as the D-Day announcement they made in 1995. It's good fodder for the software industry, it should wake a lot of people up, and open up some closed boxes, which is a good thing. Dann Sheridan had this to say after a concept meeting held last summer: In addition to the brief diagram they drew, we discussed the specific types of services that would be offered. Here are the categories -- application, library, transactional, and utilities. Application services would include things like Office, Great Plains, Visio, etc. Library services would include access to advanced C# libraries like those produced by Dundas, advanced ASP+ components, and other high value functionality for developer to embed in their applications. Transactional services would include payments, purchases, settlements, funds transfers, etc. Utility services would include things like back-up and restore services, disk watchers, all types of system monitoring, etc. You can't do this stuff without some kind of router. Feel like a Hailstorm yet? You better believe it. Sounds like the stage is set for a major reshaping of our entire world. Anybody with deeper knowledge care to comment?
This certainly could define the delivery method for .Net assemblies. Imagine thousands of catalogued components available through an MSN component service, and metered out pay-per-use or subscription. The magnitude of the announcement tomorrow sheds a little light on why Ballmer wasn't concerned about the "oh yeah .Net will run on Linux we're going to announce that next week" slip. Microsoft is very good at winning the battles they want or need to win, but don't think Microsoft is set to destroy the add-on software or ISV markets. I for one doubt that Hailstorm is going to be anything other than a new delivery method for the value that we, and thousands of other ISVs add to MS's offerings. My $.02, David
-
Ok guys time to fess up what you know, let's see if we can get some juice on this. On Monday MS is set to announce the scope and breadth of the next version of Microsoft Instant Messenger, codenamed Hailstorm. Thing is that the rumor mill has Hailstorm including everything from on-line web storage, to software components, to an advanced peer to peer distributed computing architecture (the routing, cataloging, and transaction engine for SOAP) and more. The general consensus is that Microsoft basically cloned Jabber wholesale and used it as the foundation for Microsoft's web services delivery system. Dave Winer, of UserLand (and contributor to the SOAP spec) had this to say after attending an invite-only NDA event in Redmond: If you're a reporter and thinking you know what they're going to talk about on Monday, trust me, you don't. Go, and listen, and think. Their plan is as big as the D-Day announcement they made in 1995. It's good fodder for the software industry, it should wake a lot of people up, and open up some closed boxes, which is a good thing. Dann Sheridan had this to say after a concept meeting held last summer: In addition to the brief diagram they drew, we discussed the specific types of services that would be offered. Here are the categories -- application, library, transactional, and utilities. Application services would include things like Office, Great Plains, Visio, etc. Library services would include access to advanced C# libraries like those produced by Dundas, advanced ASP+ components, and other high value functionality for developer to embed in their applications. Transactional services would include payments, purchases, settlements, funds transfers, etc. Utility services would include things like back-up and restore services, disk watchers, all types of system monitoring, etc. You can't do this stuff without some kind of router. Feel like a Hailstorm yet? You better believe it. Sounds like the stage is set for a major reshaping of our entire world. Anybody with deeper knowledge care to comment?
more Hailstorm info... During the next six months, Microsoft will offer a free suite of end-user Web services that it believes will draw a global Internet membership numbering as many as 100 million within a year. The prospect of this massive audience – not mere passive Web surfers but users of services, and not only consumers but also corporate users – will be the bait to draw developers and Web site operators to the platform. A Microsoft evangelism team led by 35-year-old VP Sanjay Parthasarathy is targeting high-profile Web site operators and enterprises to buy into the plan. EBay has already joined and other partners will be announced Monday. http://www.thestandard.com/article/display/0,1151,22946,00.html
-
more Hailstorm info... During the next six months, Microsoft will offer a free suite of end-user Web services that it believes will draw a global Internet membership numbering as many as 100 million within a year. The prospect of this massive audience – not mere passive Web surfers but users of services, and not only consumers but also corporate users – will be the bait to draw developers and Web site operators to the platform. A Microsoft evangelism team led by 35-year-old VP Sanjay Parthasarathy is targeting high-profile Web site operators and enterprises to buy into the plan. EBay has already joined and other partners will be announced Monday. http://www.thestandard.com/article/display/0,1151,22946,00.html
Well - this is what we were all promised at PDC last July when Gates unvieled the .NET strategy. Fun times ahead! (Anyone got Bill's number handy? I should have a chat with him about this ;) ) cheers, Chris Maunder
-
Ok guys time to fess up what you know, let's see if we can get some juice on this. On Monday MS is set to announce the scope and breadth of the next version of Microsoft Instant Messenger, codenamed Hailstorm. Thing is that the rumor mill has Hailstorm including everything from on-line web storage, to software components, to an advanced peer to peer distributed computing architecture (the routing, cataloging, and transaction engine for SOAP) and more. The general consensus is that Microsoft basically cloned Jabber wholesale and used it as the foundation for Microsoft's web services delivery system. Dave Winer, of UserLand (and contributor to the SOAP spec) had this to say after attending an invite-only NDA event in Redmond: If you're a reporter and thinking you know what they're going to talk about on Monday, trust me, you don't. Go, and listen, and think. Their plan is as big as the D-Day announcement they made in 1995. It's good fodder for the software industry, it should wake a lot of people up, and open up some closed boxes, which is a good thing. Dann Sheridan had this to say after a concept meeting held last summer: In addition to the brief diagram they drew, we discussed the specific types of services that would be offered. Here are the categories -- application, library, transactional, and utilities. Application services would include things like Office, Great Plains, Visio, etc. Library services would include access to advanced C# libraries like those produced by Dundas, advanced ASP+ components, and other high value functionality for developer to embed in their applications. Transactional services would include payments, purchases, settlements, funds transfers, etc. Utility services would include things like back-up and restore services, disk watchers, all types of system monitoring, etc. You can't do this stuff without some kind of router. Feel like a Hailstorm yet? You better believe it. Sounds like the stage is set for a major reshaping of our entire world. Anybody with deeper knowledge care to comment?
According to Wininformant (http://www.wininformant.com/Articles/Index.cfm?ArticleID=20338), Hailstorm is the codename for the .NET initiative. Regards, Peter Pearson
-
Ok guys time to fess up what you know, let's see if we can get some juice on this. On Monday MS is set to announce the scope and breadth of the next version of Microsoft Instant Messenger, codenamed Hailstorm. Thing is that the rumor mill has Hailstorm including everything from on-line web storage, to software components, to an advanced peer to peer distributed computing architecture (the routing, cataloging, and transaction engine for SOAP) and more. The general consensus is that Microsoft basically cloned Jabber wholesale and used it as the foundation for Microsoft's web services delivery system. Dave Winer, of UserLand (and contributor to the SOAP spec) had this to say after attending an invite-only NDA event in Redmond: If you're a reporter and thinking you know what they're going to talk about on Monday, trust me, you don't. Go, and listen, and think. Their plan is as big as the D-Day announcement they made in 1995. It's good fodder for the software industry, it should wake a lot of people up, and open up some closed boxes, which is a good thing. Dann Sheridan had this to say after a concept meeting held last summer: In addition to the brief diagram they drew, we discussed the specific types of services that would be offered. Here are the categories -- application, library, transactional, and utilities. Application services would include things like Office, Great Plains, Visio, etc. Library services would include access to advanced C# libraries like those produced by Dundas, advanced ASP+ components, and other high value functionality for developer to embed in their applications. Transactional services would include payments, purchases, settlements, funds transfers, etc. Utility services would include things like back-up and restore services, disk watchers, all types of system monitoring, etc. You can't do this stuff without some kind of router. Feel like a Hailstorm yet? You better believe it. Sounds like the stage is set for a major reshaping of our entire world. Anybody with deeper knowledge care to comment?
This will answer many questions: http://www.microsoft.com/net/hailstorm.asp To see shots of it in action click on the partner links here: http://www.microsoft.com/presspass/events/hailstorm/ Looks pretty awesome Josh
-
Ok guys time to fess up what you know, let's see if we can get some juice on this. On Monday MS is set to announce the scope and breadth of the next version of Microsoft Instant Messenger, codenamed Hailstorm. Thing is that the rumor mill has Hailstorm including everything from on-line web storage, to software components, to an advanced peer to peer distributed computing architecture (the routing, cataloging, and transaction engine for SOAP) and more. The general consensus is that Microsoft basically cloned Jabber wholesale and used it as the foundation for Microsoft's web services delivery system. Dave Winer, of UserLand (and contributor to the SOAP spec) had this to say after attending an invite-only NDA event in Redmond: If you're a reporter and thinking you know what they're going to talk about on Monday, trust me, you don't. Go, and listen, and think. Their plan is as big as the D-Day announcement they made in 1995. It's good fodder for the software industry, it should wake a lot of people up, and open up some closed boxes, which is a good thing. Dann Sheridan had this to say after a concept meeting held last summer: In addition to the brief diagram they drew, we discussed the specific types of services that would be offered. Here are the categories -- application, library, transactional, and utilities. Application services would include things like Office, Great Plains, Visio, etc. Library services would include access to advanced C# libraries like those produced by Dundas, advanced ASP+ components, and other high value functionality for developer to embed in their applications. Transactional services would include payments, purchases, settlements, funds transfers, etc. Utility services would include things like back-up and restore services, disk watchers, all types of system monitoring, etc. You can't do this stuff without some kind of router. Feel like a Hailstorm yet? You better believe it. Sounds like the stage is set for a major reshaping of our entire world. Anybody with deeper knowledge care to comment?
Interesting article about Hailstorm on The Register: http://www.theregister.co.uk/content/4/17709.html D
-
Ok guys time to fess up what you know, let's see if we can get some juice on this. On Monday MS is set to announce the scope and breadth of the next version of Microsoft Instant Messenger, codenamed Hailstorm. Thing is that the rumor mill has Hailstorm including everything from on-line web storage, to software components, to an advanced peer to peer distributed computing architecture (the routing, cataloging, and transaction engine for SOAP) and more. The general consensus is that Microsoft basically cloned Jabber wholesale and used it as the foundation for Microsoft's web services delivery system. Dave Winer, of UserLand (and contributor to the SOAP spec) had this to say after attending an invite-only NDA event in Redmond: If you're a reporter and thinking you know what they're going to talk about on Monday, trust me, you don't. Go, and listen, and think. Their plan is as big as the D-Day announcement they made in 1995. It's good fodder for the software industry, it should wake a lot of people up, and open up some closed boxes, which is a good thing. Dann Sheridan had this to say after a concept meeting held last summer: In addition to the brief diagram they drew, we discussed the specific types of services that would be offered. Here are the categories -- application, library, transactional, and utilities. Application services would include things like Office, Great Plains, Visio, etc. Library services would include access to advanced C# libraries like those produced by Dundas, advanced ASP+ components, and other high value functionality for developer to embed in their applications. Transactional services would include payments, purchases, settlements, funds transfers, etc. Utility services would include things like back-up and restore services, disk watchers, all types of system monitoring, etc. You can't do this stuff without some kind of router. Feel like a Hailstorm yet? You better believe it. Sounds like the stage is set for a major reshaping of our entire world. Anybody with deeper knowledge care to comment?
Some good info (including screenshots) of HailStorm can be found here. cheers, Chris Maunder