All geek questions in one place

Convert web application to web service

a. What should I consider? b. I have several stored procedures executed by the current application. If I create equivalent methods to perform these procedures, what would be the risk or problem.

+3
source share
4 answers

Architecturally, one thing you should consider when converting a web application to a web service is that local access to methods and data does not match remote access. Remote access should be designed so that calls are clearer and exchange information at the same time.

Another thing you need to think about is what you will use in your serialization protocol. For example, SOAP and a REST-based protocol.

Also think about security — security considerations vary between web application and web service.

Finally, think about how others will find out about your web service (or if any).

+2
source

One risk is that your code stays the same.

What I mean is that in this situation there is a clear possibility of code duplication, and as such means that you may accidentally forget to change one of the places where this procedure is stored (say, if you add a new variable to the saved call proc).

. , -, , , . , / .

0

, , , . , -, -. - .

- . . , , Windows.net TCP. , .net- java-, , .

WCF ASMX. .

0

, , , , . , .

- - . "" , .

" ": , , . ? , . , .

0

Source: https://habr.com/ru/post/1704284/

More articles:


All Articles