Updated: 26-06-2003; 18:53:19.
Nielsen's Weblog
.NET [use your Context dude]
        

1. juni 2003

I spend the better part of my weekend setting up my laptop again, thanks to trojans and hackers. thanks allot guys. I see I still have lots of software to install, baaah.

I upgraded my firewall and now I have a password long as an Anaconda >:)

"Ignorance is bliss"
-- Cypher


7:21:15 PM    comment []

New book is up, looking forward to this.


7:19:08 PM    comment []

There was an interesting article on fawcette, written by Jimmy Nilsson. I just had to comment on the article (mainly because DataSetS looked bad by the end of the article), so I wrote him an email, after some ping pong emails about DataSetS and custom collections, an interesting question popped up: "is System.Runtime.Remoting going to be absolete in a couple of years?". I think YES, or at least we will refer to .net remoting as legacy code in about 1.5 years from now. The way I see this, there are greater forces, pushing doc/literal support for the entire .net framework so imo .net remoting will 'die' eventually BUT: Interoperability and cross-platform support is the future and a major gold mine for consultants, it's where the big money can be found. Integrating systems, especially heterogeneous systems ... .net remoting has no business there, neither has RMI, ask anybody involved with WS-I.

At the time the ".NET" buzzword landed on managers desk, the word was "software as a service". Today this still applies and the name is now Mr. SOA, Service Oriented Architecture,  the new breed in distributed computing. There seems to be a distinction between Webservice, SOA and Interoperability. Today you can wrap any legacy component in a webservice and thereby potentially achieve cross-platform support and integration to other systems(heterogeneous or homogeneous). Where as wrapping existing legacy component in standard webservice bodies, surly is the future bread and butter of consultants, SOA will bring some challenges to the table. SOA is about architecturing webservices e.i well defined functions that doesn't depend on other webservices.

I had a discussion with a colleague about 3 webservices in 3 different namespaces each depending on each other. Custom type support broke his architecture in the end.

SOA will require consultants/corporate to think extra about architecture, SOA tools will emerge from everywhere. Biztalk Server ver. 10, service pack 21 will hit the streets next year around this time :-).

Anyway .NET remoting as you know it today, will have another name and face in year 2005. Webservice are thy name, not just a buzzword anymore, it's bread and butter. Ask me again in year 2005 >:)

Jimmy Nilsson wrapped up our email session, asking the question, if .net remoting will disappear what about smart clients then ? .... nothing you can't wrap in webservice.


 


7:11:48 PM    comment []

© Copyright 2003 Allan Nielsen.
 
June 2003
Sun Mon Tue Wed Thu Fri Sat
1 2 3 4 5 6 7
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24 25 26 27 28
29 30          
May   Jul


Click here to visit the Radio UserLand website.

Subscribe to "Nielsen's Weblog" in Radio UserLand.

Click to see the XML version of this web page.

Click here to send an email to the editor of this weblog.