Bear Bibeault wrote:I would assume that you're handling login on the server, so it'd make the most sense to generate the cookie after the user has been authenticated. You are also protecting traffic with SSL, right?
Bear Bibeault wrote:Cookies
Tim McGuire wrote:
mark I thomas wrote:I already tested my code (by the way it was not from any google..). But I didn't feel 100% sure if I can overwrite an existing timeinMillion so I don't know if there is any potential problem -- and that's why I posted the question.
Tim's response started with "Not really..." puzzled me because I didn't know what that "not really.." menas so I was interested in hearing more from that part but unfortunately I didn't get any insight from him.
I thought when someone said "not really..." he must have something interesting in his mind and that's what I expected to hear and discuss with that person.
Tim's second email even confused me more --- It seems he was asking me "If you think there is no problem then why bother asking ?" Well, Most people believe they write the correct code but people still do code review in team, your peers may identify some potential issue that you don't see -- That's exactly why I posted that question.
I think I am very cool.
You are cooler than the other side of the pillow.
when you asked " I want to get a Calendar that is on the same day as "12345678L" but is at 6:00AM. Does this code achieve that ? "
I said "not exactly" because I wanted you to see that what you thought was 6:00 was actually 6:00:45. For my alarm clock in the morning, then this is good enough. For the mars lander, maybe not.
When you said the code worked for you anyway, it became funny because I had identified a potential issue but the requirements began shifting under us.
Tim McGuire wrote:
mark I thomas wrote:I already tested my code (by the way it was not from any google..). But I didn't feel 100% sure if I can overwrite an existing timeinMillion so I don't know if there is any potential problem -- and that's why I posted the question.
Tim's response started with "Not really..." puzzled me because I didn't know what that "not really.." menas so I was interested in hearing more from that part but unfortunately I didn't get any insight from him.
I thought when someone said "not really..." he must have something interesting in his mind and that's what I expected to hear and discuss with that person.
Tim's second email even confused me more --- It seems he was asking me "If you think there is no problem then why bother asking ?" Well, Most people believe they write the correct code but people still do code review in team, your peers may identify some potential issue that you don't see -- That's exactly why I posted that question.
I think I am very cool.
You are cooler than the other side of the pillow.
when you asked " I want to get a Calendar that is on the same day as "12345678L" but is at 6:00AM. Does this code achieve that ? "
I said "not exactly" because I wanted you to see that what you thought was 6:00 was actually 6:00:45. For my alarm clock in the morning, then this is good enough. For the mars lander, maybe not.
When you said the code worked for you anyway, it became funny because I had identified a potential issue but the requirements began shifting under us.
Tim McGuire wrote:if you say it is good enough, then it is good enough! How could I have a problem with that?