texte = 664 --001a113d5ecef465a0053f505caf Content-Type: text/plain; charset=UTF-8 Hi all, Got the user password issue resolved. Now on to user sessions. I looked in the archives and saw conversations between a lot of you regarding this topic. Ken found some issues with the encoding methods (other than base64) working properly. Some recommended using a sessions.db With the passage of time and enhancements made to WebDNA since then. I was wondering what the prevailing thoughts are on maintaining user sessions. I will most likely have a maximum of 20-25 users logged in at once. For most of their shift they won't be very active. their activities will pretty much follow the below: Login Display systems that need to be worked on for that shift (from a pre-defined search) Enter a key list for the vehicle keys they check out Open a ticket for the first system being worked on (creates work ticket to avoid losing any data) Close the ticket (updates work ticket) Repeat until shift is over Check keys back in from previous list. They may be occasionally searching the knowledge base I wrote in WebDNA. The one other thing, hence creating the work ticket on opening it, is that some of the techs will switch back and forth between their phones and tablets. I realize I can't carry the session from one device to another. I will set the session timeout to be 5-6 hours as the single longest task they might have to do is 3-4 hours long. I'm not as concerned as some were in the archive posts about security. I will encrypt the cookies or at least obfuscate them. I won't store the username and password in clear text. I'm curious as to what pros and cons you have found with either method. Thank you for your insight. Dale --001a113d5ecef465a0053f505caf Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi all,
Got the user password issue res= olved. Now on to user sessions.
I looked in the ar= chives and saw conversations between a lot of you regarding this topic. Ken= found some issues with the encoding methods (other than base64) working pr= operly. Some recommended using a sessions.db
With = the passage of time and enhancements made to WebDNA since then. I was wonde= ring what the prevailing thoughts are on maintaining user sessions.=C2=A0
I will most likely have a maximum of 20-25 users lo= gged in at once. For most of their shift they won't be very active. the= ir activities will pretty much follow the below:
L= ogin
Display systems that need to be worked on for that shift (fr= om a pre-defined search)
Enter a key list for the vehicle keys th= ey check out
Open a ticket for the first system being worked on (= creates work ticket to avoid losing any data)
Close the ticket (u= pdates work ticket)=C2=A0
Repeat until shift is ov= er
Check keys back in from previous list.
They may be occasionally searching the knowledge base I wr= ote in WebDNA.
The one other thing, hence creating= the work ticket on opening it, is that some of the techs will switch back = and forth between their phones and tablets. I realize I can't carry the= session from one device to another.=C2=A0
I will = set the session timeout to be 5-6 hours as the single longest task they mig= ht have to do is 3-4 hours long.
I'm not as co= ncerned as some were in the archive posts about security. I will encrypt th= e cookies or at least obfuscate them. I won't store the username and pa= ssword in clear text.=C2=A0
I'm= curious as to what pros and cons you have found with either method.=C2=A0<= /div>
Thank you for your insight.
Dale
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list