android call. how net webservice for user authentication

            
android call. net webservice, when the login user name and password sent in webservice verify the validity of the results returned to the android, and this has been achieved, but the next call webservice in other ways how to determine whether it is already registered? Each method is not required to carry the user name and password every time validation? android beginner, please advise!
Reply:
Well not popular android version
Reply:
Theoretically, when the need is to call a method to detect the user name and password. This is the most stringent. But you can be controlled according to the client, if the client through the login authentication, then he has landed default, the program exposed to his service-side interface is the default landing him as if he launched landed in the client should not be these server interfaces exposed. However, the recommended each time you visit the conduct check, front and back simultaneously check a lot of sophisticated software essential elements.
Reply:

reference to the second floor wlcw16 reply:

theoretically invoke methods need to detect when a user name and password. This is the most stringent. But you can be controlled according to the client, if the client through the login authentication, then he has landed default, the program exposed to his service-side interface is the default landing him as if he launched landed in the client should not be these server interfaces exposed. However, the recommended each time you visit the conduct check, front and back simultaneously check a lot of sophisticated software essential elements.

We now use the webservice test is open, meaning that as long to get to the url can be accessed, this is clearly not, then how to verify it, or how to save the state of a user logged in it?
Reply:
To search for a long time but could not find a better solution ~!
Reply:
Project approach I've done before:
A landing when the server sends the user name and password, the server will return to give us a user ID, the user ID is a server-side generated (based on user-bound) by certain rules.
2 next each visit other methods need to bring the user Id, the server will monitor whether the user based on the user login ID.
This does not require a user name and password each time carrying unsafe and cumbersome

Reply:
Currently used is the string back to the android client a similar token encrypted after login after this string is passed to the user name and password encryption, the other webservice function call must each carry this token, each doing verification, and this token and username password just a relationship, so they do not modify these two parameters are the same every time, do not know if there was a better solution?
Reply:

references, 5th Floor leizuishuai201314 reply:

project approach I've done before:
A landing when the server sends the user name and password, the server will return to give us a user ID, the user ID is a server-side generated (based on user-bound) by certain rules.
2 next each visit other methods need to bring the user Id, the server will monitor whether the user based on the user login ID.
This does not require a user name and password each time carrying unsafe and trouble

My reply is this meant. A better solution is not clear, but it is the most commonly used
Reply:
hello now get, as you say,,,, android call webservice realized login!!! rookie! request code can be sent to me to help you?

380551369@qq.com
Reply:
Find code 973249316@qq.com
Reply:
Ask the landlord with example code, are learning android call webservice achieve login feature, please enlighten me.
846025497@qq.com