POS system - PHP, Apache, MySQL, Java

Anon

I am creating a Point of sales (POS) System with PHP, Apache, MySQL, Java, and Javascript. It will be used in a retail setting with multipl clients. There will be one Linux server with 4 Win98 clients. The client's interface will be either Netscape or IE browser. Furthermore, a cash drawer and a small thermal printer (very similar to a credit card terminal printer) will be attached to the client's computer. Any advice will be greatly appreciated.

Thanks.

Kai

Anon

Advice on which part? It's usualy a good idea to ask more specific questions as general ones are kinda hard to figure out. I guess a better way to put this would be, what do you already understand and what do you need to know?

Anon

First of all, I have done extensive searches and was not able to find any past references regarding a POS system using PHP, Apache, etc.

Without any references, I was not sure if this project is feasbile. This is my current thought process:

Linux server with PHP4, Apache, and MySQL.
All dynamic contents will be written in PHP including authenication (log-in) for clerks, buying process (very smiliar to on-line ecommerce with a shopping cart), dynamic inventory control, charge accounts, session tracking, and etc...
MySQL will server as backend. It will provide customer, user, inventory, etc databases.
Win98 with IE / Netscape as client's interface.
Java applets will control the CC terminal type thermal printer and open the cash drawers attached to the Win98 clients. This will occur at the end of buying process.

Now, back to my question. Does any one have any experience with using PHP for a POS system? Is this project feasbile? Any suggestions / recommendation is greatly appreciated.

Thanks for you time.

Anon

Sounds a lot like a standard e-commerce website with a few extras... I didn't think Java was allowed to access the low level hardware like printers and stuff, I thought that would go against it's security protocols?

One thing to watch out for with using php is the math functions not being 100% precise, I found that every now and then I'd loose a few decimal points which with big purchases can mean the diference between paying $10 and $100 for tax.

Other than that it's got potential. Doing the entire system using a standard web interface will reduce the development time by a considerable amount as well as make it easier to update, no having to recompile the whole interface for every little upgrade.