16,004,564 members
Sign in
Sign in
Email
Password
Forgot your password?
Sign in with
home
articles
Browse Topics
>
Latest Articles
Top Articles
Posting/Update Guidelines
Article Help Forum
Submit an article or tip
Import GitHub Project
Import your Blog
quick answers
Q&A
Ask a Question
View Unanswered Questions
View All Questions
View C# questions
View C++ questions
View Javascript questions
View Visual Basic questions
View .NET questions
discussions
forums
CodeProject.AI Server
All Message Boards...
Application Lifecycle
>
Running a Business
Sales / Marketing
Collaboration / Beta Testing
Work Issues
Design and Architecture
Artificial Intelligence
ASP.NET
JavaScript
Internet of Things
C / C++ / MFC
>
ATL / WTL / STL
Managed C++/CLI
C#
Free Tools
Objective-C and Swift
Database
Hardware & Devices
>
System Admin
Hosting and Servers
Java
Linux Programming
Python
.NET (Core and Framework)
Android
iOS
Mobile
WPF
Visual Basic
Web Development
Site Bugs / Suggestions
Spam and Abuse Watch
features
features
Competitions
News
The Insider Newsletter
The Daily Build Newsletter
Newsletter archive
Surveys
CodeProject Stuff
community
lounge
Who's Who
Most Valuable Professionals
The Lounge
The CodeProject Blog
Where I Am: Member Photos
The Insider News
The Weird & The Wonderful
help
?
What is 'CodeProject'?
General FAQ
Ask a Question
Bugs and Suggestions
Article Help Forum
About Us
Search within:
Articles
Quick Answers
Messages
Comments by Amol M Vaidya (Top 2 by date)
Amol M Vaidya
20-Aug-14 22:04pm
View
obviously you will need the documentation to know the APIs that came with the device. You can setup a windows app service that can communicate with the device if you want to support all OS platforms. If only IE is your target you may write a simple activex control to handle this stuff
Amol M Vaidya
20-Aug-14 21:18pm
View
i think what you want is that a user id can login only from one location at a time. No Simultaneous logins allowed.
well the best option is to put a flag in the DB or some place when the user logs in and on logout or session timeout you clear that flag. This will allow you to check the bit when the same ID tries to login again from different browser or location.
the only tricky part is the clearing the bit on session time out. Make use of the session events in the global.asax file to handle these cases