.NET is clouded somewhat, since they use the name for every product coming out this year (instead of 2001:-) ).
What they really want to do, and what they're pushing in those lame commercials, is basically exposing webapplications to the internet as distributed objects, so that you can e.g. build a "wedding agency" by building a portal from a travel agency webservice, flower shop webservice, dress rental service, etc. Pick services and compose a webapplication.
What the "vision" boils down to is that ".NET" will implement something like CORBA, DCOMM or RMI over the internet. Using XML over HTTP as transport (to bypass firewalls... "we haven't thought of security yet"(quote)), and splitting the ORB/REGISTRY function in two. UDDI servers will be the "yellow pages", and Biztalk servers will do the negotiation, etc.
What they want to cash in on is: .NET enabled tools (hence the SQLServer.NET, et. al)
UDDI and Biztalk servers.
C# is just MS needing a "real" language (instead of VB) and not wanting to use Java, etc. It has nothing to do with.NET.
All the world needs to do if we want to join in on this internet-distributed services project is to read up on XML, SOAP and UDDI, and make our own resource brokers (like Biztalk will be). Those who want can enhance their favourite editor/IDE to make working with these standards easier.
-e
I've read in a norwegian mag that the canadians already have that kind of bandwith for their university/state backbone. According to the article, the Canadians were putting final touches on a upgrade to 40Gb capacity. Sorry, but I have no references. Any Canadians who can confirm/dismiss this?
I know I wanted to emigrate when I read about it. Heck, Canada's much further south as well. Practically tropical climate for me:)
Once you have set up your design, review it, using proper tools for authentication logic. Start with BA N logic. Although old, it will catch most serious glitches. Then consider using some of the more complex tools available, like GNY.
Even the most sophisticated ciphers won't help if your protocol design is flawed. (original Kerberos was vulnerable to replay attacks). A clean protocol does not have to be complex. The wide mouthed frog protocol only uses three messages.
Remember freshness. A l/p scheme should at least have some form of challenge/response funcionality added to it. This does not have to be visible (add complexity) to the user. See a simple c/r scheme used by PHPlib (check the source).
Ok, I trailed off from the question, but anyone interested in authentication, and haven't already read academic papers on the subject, should check out the works of Burrows and friends.
Crossroads also comes in a print edition, and I got my "linux" edition a week or two ago. It's part of the ACM "Student package" deal. Pretty nice deal, btw: you get "crossroads", "communications" and a nifty @acm.org email adress. Best part of it all is access to the ACM digital library, loaded with many of the most important papers in CS history.
And if you do as we managed, you convince your administration to sponsor the member fee:) - eivind (Norway)
Slashdot Mirror
.. isn't it more than 5??
.NET is clouded somewhat, since they use the name for every product coming out this year (instead of 2001 :-) ).
.NET enabled tools (hence the SQLServer.NET, et. al)
.NET.
What they really want to do, and what they're pushing in those lame commercials, is basically exposing webapplications to the internet as distributed objects, so that you can e.g. build a "wedding agency" by building a portal from a travel agency webservice, flower shop webservice, dress rental service, etc. Pick services and compose a webapplication.
What the "vision" boils down to is that ".NET" will implement something like CORBA, DCOMM or RMI over the internet. Using XML over HTTP as transport (to bypass firewalls... "we haven't thought of security yet"(quote)), and splitting the ORB/REGISTRY function in two. UDDI servers will be the "yellow pages", and Biztalk servers will do the negotiation, etc.
What they want to cash in on is:
UDDI and Biztalk servers.
C# is just MS needing a "real" language (instead of VB) and not wanting to use Java, etc. It has nothing to do with
All the world needs to do if we want to join in on this internet-distributed services project is to read up on XML, SOAP and UDDI, and make our own resource brokers (like Biztalk will be). Those who want can enhance their favourite editor/IDE to make working with these standards easier.
-e
I know I wanted to emigrate when I read about it. Heck, Canada's much further south as well. Practically tropical climate for me :)
- eivind
Anyone designing/reviewing an authenticeation scheme, should start with reading basic background info, like Pr udent engineering practice for cryptographic protocols" and related papers.
Once you have set up your design, review it, using proper tools for authentication logic. Start with BA N logic. Although old, it will catch most serious glitches. Then consider using some of the more complex tools available, like GNY.
Even the most sophisticated ciphers won't help if your protocol design is flawed. (original Kerberos was vulnerable to replay attacks). A clean protocol does not have to be complex. The wide mouthed frog protocol only uses three messages.
Remember freshness. A l/p scheme should at least have some form of challenge/response funcionality added to it. This does not have to be visible (add complexity) to the user. See a simple c/r scheme used by PHPlib (check the source).
Ok, I trailed off from the question, but anyone interested in authentication, and haven't already read academic papers on the subject, should check out the works of Burrows and friends.
- eivindCrossroads also comes in a print edition, and I got my "linux" edition a week or two ago. It's part of the ACM "Student package" deal. Pretty nice deal, btw: you get "crossroads", "communications" and a nifty @acm.org email adress.
Best part of it all is access to the ACM digital library, loaded with many of the most important papers in CS history.
And if you do as we managed, you convince your administration to sponsor the member fee :) - eivind (Norway)