Hi!
Sacha Labourey skrev:
>
> Hello,
>
> This may be out-of-topic but on many retail softwares, the database is
> replicated on every cash registers, thus suppressing your serialisation
> problem (but creating a new synchronisation issue).
>
> If not replicated, what happen when there is a network or server outage?
> every customer go back home? they wait for your technician?... If your cash
> register is completely independant of the server (stand-alone), as long as
> your cash register runs, your customer are happy.
Yep, the system is designed to be able to fall back to either a local
server (if normally runned against a central server) or even to a
standalone client. And it's here that jBoss gets very interesting! Cheap
and lightwight is a perfect match when you want to distribute the app to
many small sites :) (Please don't hit me... i know that jBoss will fight
the big ones even on larger installation - but it's not always easy to
convince the peoples with power and money :(
>
> Furthermore, some very stressing database queries can occur if you need to
> implement some kind of "matching" i.e. if you buy two cans of bier, every
> peanuts bought are 50% off.
You kidding :)
>
> My considerations may be out of topic for what you are trying to achieve. In
> this case, just forget it! ;)
Out of topic, maybe but it's cool with some more that has an eye on the
retail market :)
/Lennart
>
> Cheers,
>
> Sacha
>
> > -----Message d'origine-----
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> List Help?: [EMAIL PROTECTED]
--
mailto:[EMAIL PROTECTED]
http://www.benefit.se/english
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
