Oops. S/b "The concept of 'wins' does *NOT*  have meaning for me"

---

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk

If I login at machine A I can do some work.  If I then move to machine B and I can login but automatically will be logged out from machine A. Vice versa, if I now login to machine A again I will be logged out from machine B and so on...

The goal is to prevent users having to pay for their accounts from passing their credentials to other people and using one account together.

A custom login / authentication provider syncronized with users online would be a possible viable approach.

But the main issue is still actually understanding/knowing when a user is no longer online.  If a user has browsed away to another site - but not closed their browser then the session is still the same.

Also if the user has tabbed to a new page - and the site is still open then they are still online - but we dont really know if they are or not.

One option would be a ajax callback buried in your skin - that calls back to the server once a minute say to confirm the users is possibly still online.

it is something that could be achieved fairly effectively - with some custom coding.

Mind it would be much easier to prevent new logins that trying to force a logout from a different session.  Session management is controlled by the server a pretty low and can be a little messy to work with at times.

Westa