Josh said:
Yeah I follow what your saying. But everytime you use the same instance of
a webservice on the PDA it should have the same session id?
Depends on wheter it returns ie. quits, or if it runs in some kind of loop?
If you call the function several times its a new instance each time, even
though its a button in your PDA program that you just press 10 times in a
row to call the web service 10 times ie. 10 instances.
If you keep it in a loop, and its not ending. Well, then i guess it should
be the same session.
ie. The process is the same, the webservice instance is the same all thats
different is the function I call.
Which in my mind at the moment its behaving like a new process or instance
is started?
Exactly.
If thats the way it is, its pretty crap? any work arounds?
Well actually i do agree. It would be much easier for it to stay alive over
multiple webservice call from the same caller. But even though i can see
that it might be difficult to maintain.
The workarounds depends on what you wanna do. I dont use sessions for
anything anymore. For storing data for the same session i use a database,
for unique ids i use guids. I guess for anything else you have to send some
kind of id forth and back between the PDA and the webservice as a parameter
or something like that.
I used to store the active users on my website in a session variable, but
now its active as long as the program runs. I keep all the maintenance of
logging in, in my PDA app. Encryption might be a good thing here.
Its more work, but to be honest the app. runs much faster than my website
did. So i win in the end
Jimmy