.NET for Apache
PerlGuy was so kind as to forward us the news about the joint Apache/Microsoft combined press conference scheduled from Wednesday at the OSCON Quote: "We will announce news related to the Apache web server and Microsoft's
development technology, .NET. This should be one of the biggest
announcements of the conference..."
The email he recieved: Covalent Technologies will be holding a press conference at the O'Reilly
Conference on Wednesday at 3:15 in suite 415 (during the afternoon break).
We will announce news related to the Apache web server and Microsoft's
development technology, .NET. This should be one of the biggest
announcements of the conference and an interesting follow up to Microsoft's
appearance last year at the show as well as to their general comments on
open source. Executives will be on hand to answer questions or to conduct
one-on-one interviews after the announcement.
Kinda offtopic, but the newest version of edonkey is .net based. Is it worth it to install all that .net shit (also for future programs). I'm just using the command line version now.
Who is the fucking moron who moderated this as "flamebait"?
From looking back at the history of that and the interactions with Apple, it looks like Microsoft killed it. Told Apple, 'we don't want you doing this' and Apple looked at the costs, the earliness of the paradigm (document-oriented not application-oriented), and Microsoft's obvious objection to the technology being out there, and *sniccckt!* killed it on command. It got 'Steved', and it was out there being used, the base of a brilliant internet suite of functionalities, the base of a set of technology startups building stuff to work with the new way of doing things.
That was OpenDoc, which threatened Microsoft's Office dominance by undercutting the whole application model. It existed, it was out there being used. The fact that you're looking to .NET to do this is pretty obscene, considering the history. Microsoft won't be letting you do this. Not unless they start charging per use-of-embedded-object...
Any company which cannot maintain HTTP compliance in their streaming media solution, yet fails to release the source code to the public which would ensure standards compliance has no business at all in the open source domain.
Unfortunately, Microsoft does not keep the revision history of the development of their software online, otherwise I could offer substantial proof.
However, I can attest to the fact that with every other release, until Windows Media Player 8, the HTTP streaming component of that product was broken.
I do not really care about their agressive/malicious tactics to keep other software products from complying with their stuff. When these tactics are employed, the open source community stays away. The problem will become apparent when their software just does not work with apache's one day, because they goofed. Companies will deem Apache as unstable and move to the ever stable and compliant IIS solution.
-kali
Thoughts on why this hasn't been pursued...or has it?
I apologize in advance for my utter lack of knowledge. ;-)
Microsoft are not interested in opening up their IP.
You is needing help with your tenses. Microsoft are not plural.
Put literacy before debates over software and computer empires, please.
Attention deficit disorder is a complicated issue, spanning several major... HEY LET'S GO RIDE BIKES!