[Mono-dev] WebService application model

[Mads Bondo Dydensborg]

Hi there.

Coming from a C++/Corba background (Linux) I have problems understanding the 
webservice application model of C#/.NET/Mono/whatever, and is seeking 
advice/pointers/something to get an idea of what models are feasible.

Using Corba, a SOA application is almost a "normal" application, exposing part 
of its functions/objects to "the net". The ORB handles requests, spawns 
threads, and calls into "the running application". The only "hard" part is to 
make sure that the threads do not wreck havoc on eachother.

Now, so far, what I have been able to figure out about .net webservices, looks 
like CGI to me? Clearly this can not be the case, but I lack information 
describing the application models possible/feasible. Something a bit more 
meaty than the usual [WebMethod] void HelloWorld stuff, perhaps a bit higher 
level, discussing the part the web server plays, the mapping of requests onto 
threads (or applications?) and so on.

Any advice? Pointers to information/whitepapers/books/places to post a 
question/whatever. I am quite lost, as I have been told to write a 
server/service "in c# as a webservice, using SOAP/XML", but have problems 
mapping it onto my usual model of a service, which is probably more like a 
unix deamon...

Regards,

Mads
-- 
Med venlig hilsen/Regards

Systemudvikler/Systemsdeveloper cand.scient.dat, Ph.d., Mads Bondo Dydensborg
Dansk BiblioteksCenter A/S, Tempovej 7-11, 2750 Ballerup, Tlf. +45 44 86 77 34