Tthere are many different ways to implement a kiosk application. Web browsers have a kiosk mode so one can make a web application. Java has full screen exclusive mode.
Introducing a network brings a lot of security risk so most bank ATM's are custom C/C++ applications run from a PC enclosed in the ATM's safe. Communication is usually via modem or leased line directly back to the bank.
The overall monitoring app can be written as a web app (and probably should - so the admin can check it from anywhere - like if he's on a call working on a failed kiosk ) The actual app on the kiosk can be too, with a few wrinkles. An overall working/not working can be done easily with a simple request to the machine - but this doesn't say what failed - machine could be down - broken or someone just tripped over the cord and unplugged it, or network could be out somewhere between the monitoring app and the kiosk. Monitoring the printer is a little more difficult - unless the printer has some sort of web interface that your app can query - because if your kiosk app is a web app - it's not printing directly to the printer - the web browser on that machine is - so you don't get "Out of Paper" or "Printer Disconnected" errors directly in your app. You may need a separate program to do this, depending on the printer.
Write once, run anywhere, because there's nowhere to hide! - /. A.C.
posted 10 years ago
After doing some Research on google i have come across following things
OPOS: Provides the UnifiedPOS mapping for a POS application running on the Windows operating system.
JavaPOS: Provides the UnifiedPOS mapping for a Java Language POS application running on any operating system.
POS for .NET: Provides a UnifiedPOS mapping for a Microsoft .NET POS application running on the Windows operating system with the POS for .NET class libraries.
If i have to use .NET is "POS for .NET" a good option for a web based POS.