Hi Uday, the CFID/CFTOKEN (or JSESSIONID) should indeed do the trick : when a user logs in to your site, you update a certain field in DB with CFID/CFTOKEN, and store it into a session user structure (that you certainly already have for the userid, name or something equivalent).
When the same user logs on on a different machine (or browser but that has the same effect), you update this field again (which is the same field because it's the same user). You now just have to perform a check on every request (onRequestStart method seems perfect for this) to see if field from DB matches the value defined in the user session struct. If not, onSessionEnd() etc. > >Uday, > > > >Can you expand on the reason for the single machine requirement? > > > >Folks here may be able to provide an alternate direction or solution > if we > >understand your reason for this restriction. > > > > Hi Byron, > > Gathering some information about users machine was a thought that came > in my mind while i was implementing this solution. But this was not my > purpose. My aim was to have a user logged in on ONLY one machine at > any given point. > > Thanks & Regards, > Uday > lead coldfusion developer ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:351882 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
