![]() ![]() REST doesn’t impose any kind of securities like SOAP. ![]() So whenever a user sends a request to access a resource it needs to send the token in the header so the server can identify the user, in this case, authentication does not depend on the server so there is no such condition like above. #SOAP VS REST PASSWORD#So to deal with this situation a new approach came into existence stateless, in this approach after the server authenticated the user with their email/ username and password it assigned a token to the user. Which indicated that the user is authenticated and able to access their resources like visiting their profile, but now make this example in a real situation where there are more than one servers let consider 2 in this case so we know that one server creates a session variable to authenticate the user on their end but in some case due to load balancing request is send to another server where for the given user session variable is not set, it showing unauthenticated which is not so good approach. Suppose you want to access a website and your data is hosted on the server, so to access your data you need to send the request to the server with your email and password so if your credentials are valid then the server authenticates you and sets a specific variable called as session variable to true. While discussing Web Service API it is required to know about stateful and stateless where SOAP is stateful while REST is stateless.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |