Re: alternatives to datbase dependence
On Wed, 13 Nov 2002, Matthias Solga wrote:
> > > Think of a "waiting room" widget on the doctor's interface. The
> receptionist
> > > pops a patient who has just arrived onto the "waiting list" table, and
> now
> > > the doctor's screen has to reflect it. How would you do it without
> > > notify/listen?
>
> > How about instant messaging? :-)
>
> Instant messaging could be an option, but in the daily use it is
> disturbing. That would be the worst alternative for actualizing the
> waiting queue.
Matthias,
The point was/is, there are other ways to implement notify/listen outside
of the database! Instant messaging is given as a counter-example - there
is no difference between instant messaging and notify/listen - they are
the same.
Let me elaborate :
Horst wanted a way for the doctor to be instantly notified whenever a
patient arrives in the waiting room. An instant messaging service that
connects the doctor's PC to the receptionist's device performs both sides
of the notify and listen function. Namely, the doctor's PC listens, the
receptionists' front office device notifies.
How is this more disturbing or different from Horst's widget?
Best regards,
Andrew
---
Andrew P. Ho, M.D.
OIO: Open Infrastructure for Outcomes
www.TxOutcome.Org (Hosting OIO Library #1 and OSHCA Mirror #1)
Reply to: