|
Posted by Greg D. Moore \(Strider\) on 09/02/05 02:23
"--CELKO--" <jcelko212@earthlink.net> wrote in message
news:1125612157.839762.92160@o13g2000cwo.googlegroups.com...
> "Time is what keeps everythign from happening at once!" -- George
> Karlin.
>
> Yes, parallelism is a bitch. I'd handle the multitasking by modeling
> the session/connection rather than the user, then attach the user to
> each of those. But the truth is that things were in durations -- maybe
> short ones (Aunt Mabel's photos) or long ones (disgusting_porno.com)
> and we have the problem of only being able to catch "half a fact".
>
Joe, again, I will repeat the point that many websits/pages don't have any
concept of session/connection. It's stateless.
So yes, exactly the problem is being able to catch "half a fact". The
"fact" in this case is the user requested the page at time A. Nothing more,
nothing less.
> I did a schema for a company that does a electronic timeclock system
> that recorded nothing but the id of a fob and a UTC time. The fobs are
> color coded for each job and you touch them to the mil spec timeclock
> -- it looks like a pad lock that can take a bullet at point blank
> range. If you think about it, you can do a lot with a minimal amount
> of data.
>
[Back to original message]
|