Web services better than non-serviced . Net Component
Why should we use a web service as opposed to a non-serviced .NET component?
Know the answer? Post it — somebody with the same question will find it here.
Sign in to answer this question
It is the same account you read, post and publish with — and you will come straight back to this page.
Vipul KelkarPosted Nov 1, 2011, 2:06 AM
each dealer has his own shop web site that displays some kind of product information produced by the manufacturer. So in this case, the manufacturer would host a web service that provides the product information which is consumed by several dealers in their own web sites one built in java, other on .net and so on.
So the change in product information,specification, new products etc is provided to all the dealers avoiding manual updation
Pravin MorePosted Nov 1, 2011, 1:24 AM
see,service oriented architecture have their own area of benifit over nonserviced......
1.service oriented architecture provide location independence.Therefore, an organization has the flexibility to move services to different machines, or to move a service to an external provider
Services need not be at a particular system or particular network.
2.one more benifit of service oriented architecture is--Support for Multiple Client Types:-
companies may use multiple clients and multiple client types to access a service. A PDA using J2ME may access a service via HTTP, and a SWING client may access the same service via RMI. Since the layers are split into client and service layers, different client types are easier to implement.
3.so,A service layer takes little extra effort in the beginning of a project, but the benefits are in the longtime.
i hope these points solve your query.
Thanx,
Pravin.