Hello,
I think my head is about to explode.
I have a flash application that connects to a asp.net web service. The flash application allows people to logon and query/ update the database through the web service, they can be logged on for hours and continuously be accessing the database.
I think I'm right in saying that every time the flash application queries the web service it creates a new instance of the web service.
My question is that if this is the case is it better to login and then log off the sql server every time any one function is called, or is it better to place a the login code in the global.aspx Application_Start function and then
do all the database queries under the same login?
Thanks,
Hugh
If knowlege can create problems it is not through ignorance that we will solve them.
Isaac Asimov
I think my head is about to explode.
I have a flash application that connects to a asp.net web service. The flash application allows people to logon and query/ update the database through the web service, they can be logged on for hours and continuously be accessing the database.
I think I'm right in saying that every time the flash application queries the web service it creates a new instance of the web service.
My question is that if this is the case is it better to login and then log off the sql server every time any one function is called, or is it better to place a the login code in the global.aspx Application_Start function and then
do all the database queries under the same login?
Thanks,
Hugh
If knowlege can create problems it is not through ignorance that we will solve them.
Isaac Asimov