What is the difference between programming a web service and programming a non-web service, other than marshalling and unmarshalling data?
I mean, once you get into the web service and read all of the input data or parameters, what do you do differently? Of course, I know you have to do things differently in order for the program to be a web service.
Why do so many companies want 5 years experience in developing web services if it is just a matter of normal coding after you read in or send the information from/to the calling application?
No idea about companies asking for 5 year of experience, but some things are a bit different. WS generally are called by multiple clients simultaneously, so particular attention to concurreny is required, as is tracking (who calls the WS how often, are they entitled to do that, and what to bill them). Also, a short response time is generally necessary, so performance is at a premium, as is optimizing for memory, given all the concurrent calls.
Well behaved women rarely make history - Eleanor Roosevelt. tiny ad: