Same here. Customers don't want to hear nor will they understand the
technical reason why. It just annoys the heck out of them.
Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net
-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev
Hi Malte,
The traditional solution for this kind of challenge is a message queue.
Message queues have two main ways of communicating:
- a queue acts as a post-office box: the sender puts a message into the queue
and the receiver comes and picks it up at its own pace
- a topic is like a radio stat
If you control the clients (and how they connect to the database), then
it's trivial
(think of it as a chat application :-)
- have each client register with an "update server"
- when a client changes something, it tells the "update server"
- the update server then notifies each client
If yo
Hi Malte,
On a local network, it is easy. Just broadcast on *.*.*.255. If broadcasting
somehow doesn't work, then you can just connect to all 255 addresses over UDP.
If your system has multiple IP addresses, use netstat or a similar command line
utility to get all IP addresses of the local mach
:)
On Feb 3, 2011, at 15:47, Mike Kerner wrote:
> Not yet, but I keep asking...
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription
> preferences:
> http://
Not yet, but I keep asking...
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
