On 7 June 2010 04:20, Skip Evans wrote:
> Hey Ash & all,
>
> Thanks for that detailed explanation.
>
> This is a lot of what I was thinking. Cookies can get deleted, etc, and all
> the other things that can toss wrenches into this.
>
> To clarify, they want to limit a single user to two machines m
Hey Ash & all,
Thanks for that detailed explanation.
This is a lot of what I was thinking. Cookies can get deleted,
etc, and all the other things that can toss wrenches into this.
To clarify, they want to limit a single user to two machines
max, but only one at a time.
I'm going to have to
On Sun, Jun 06, 2010 at 08:31:22PM -0500, Skip Evans wrote:
> Hey all,
>
> I'm familiar with setting cookies in PHP and using REMOTE_ADDR
> to get a visitor's IP address (or that of their gateway), but
> not quite sure how to implement a robust mechanism that would
> limit a user to logging in fro
On Sun, 2010-06-06 at 20:31 -0500, Skip Evans wrote:
> Hey all,
>
> I'm familiar with setting cookies in PHP and using REMOTE_ADDR
> to get a visitor's IP address (or that of their gateway), but
> not quite sure how to implement a robust mechanism that would
> limit a user to logging in from only
Hey all,
I'm familiar with setting cookies in PHP and using REMOTE_ADDR
to get a visitor's IP address (or that of their gateway), but
not quite sure how to implement a robust mechanism that would
limit a user to logging in from only two different machines, a
requirement this client has on the pro
5 matches
Mail list logo