Simon Fell > Its just code
Dave is talking about bootstrapping .NET, now as he'd mentioned the presense service, I'd assume he meant MSN Messenger.NET (today) & .NET My Services (future). It seems Sam assumed he meant .NET the development platform. So, now I don't know what Dave was looking to bootstrap exactly, but this adds to my belief that MS tacking .NET onto anything and everything was either a big mistake, or designed to cause confusion.
"Simon Fell wonders how they're going to handle notifications without the DIME/TCP goo. You might find the answer here. Hint: look at section 7." [Sam Ruby's Radio Weblog] Ok, now i'm confused, section 7 defines the DIME/TCP goo. DIME is optional for the HTTP binding, but as we already know, HTTP doesn't allow for unsolicited messages from the server to the client.
Peter saves me from having to find the MSN protocol links, he also has pointers for a VB implementation and the MSDN docs.
Wininfo (via xmlhack) : Sun Microsystems has cancelled plans to join a Web-services alliance that IBM and Microsoft are forming.
The current specs say that DIME is optional. [Sam Ruby's Radio Weblog] Hmmm, i wonder how they're going to handle notifications without the DIME/TCP goo.
Wow!, 4s4c 2.0 gets a clean sweap with the Axis test client ! Not bad for two Alpha code bases.
Sam raises some good points on what its going to take to talk to .NET My Services, it uses SOAP, SOAP Headers, WS-Routing [aka SOAP-RP], doc/literal style requests, kerberos authentication, encryption and signing. It'll probably use DIME and DIME over TCP binding as well. This is so far ahead of getCurrrentTemperature and the average use of SOAP today, and the obvious response is going to be look at all the unneeded complexity, but its seems to me that you can't get away with much less, given the requirements.
Looks like Ingo is a WSDL FM Fan :) Integrating Radio with .NET Remoting
Hmmm, having some upstreaming problems, it doesn't appear to be updating the archive page when i post to the home page.
The core question is -- can we communicate, via SOAP 1.1, with the .NET runtime? We need help with this because we don't have the expertise inside UserLand. That's when I ask the community to help. Help! [Scripting News]
This is my understanding of the situation, there's no SOAP enabled way to talk to the MSN Messenger cloud today, If you're on a Windows box with the MSN client installed, then there's a COM API that lets you interact with Messenger, IIRC this includes presense notifications. In addition the protocol used between the MSN client and the cloud is documented [I'll try and dig the link out] so you can build a client from scratch. Alternatively the Jabber folks have an MSN gateway, so you could write a Jabber client to get the notifications [I'd guess that a jabber client is easier to write for the folks with good XML experience], again the Jabber client is not SOAP. This all changes when Hailstorm [aka .NET My Services] ship, things seem pretty quiet on the Hailstorm front, the Passport guys have bitten off a very large problem, and Hailstorm can't ship till the new version of Passport ships.
Hey Sam, i sent you some code for the 2B & 2C interop tests, let me know if you got it or not.
Seems like my ISP is having some problems with email, IM me if you need to MSN: the_com_guy at hotmail.com Yahoo: simonfell99 ICQ: 2013522
Last update: 2/9/2003; 5:28:07 PM.
