> - I agree that a broadcast socket type solution is just "too hard".....
Not really - tho its also not easy. TVNZ (thru RealTime Technologies, I
beleive) do this for Cricket, and some game shows.
My flatmate did it for an industrial wash control app. Works VERY well.
> - Also when sending a "GET" message, I would still like that to be a SQL
> request so that I can get data into say a TQuery so that I can still use the
> functionality of DB Aware controls and the BDE/ADO/IBX etc. Not sure how I
> would handle. Workstation1: "I need some data server1" Server1: "Wait. Let
> me check that I have the latest data" Server1 "Hey Workstation 1 you can get
> your data" Workstation1 executes SQL or whatever......
why not have wks1 do:
recordPos := 1;
select * from changingtable where recordID >= :recordPos;
<read the data>
recordPos := query.recordID (get the last one)
inc(recordPos)
godoitagain.
> Sounds a bit like MIDAS, nTier to me..... Trying to stay away from that if I
> can.....
nTier is about the best way to get failover, especially CORBA.
Dont take this the wrong way, but surely writing a solid, tested,
working app would solve these problems? If you write and test your code
so it doesn't crash, and use a database that doesn't crash or corrupt
(ie, not paradox or Access), then having it fail is NOT an option??
?
N
--
Nic Wise - Chief SCUD Launcher - Inprise/Borland New Zealand
wk: 09.481.9999 x9753 cell: 021.676.418
em: [EMAIL PROTECTED]
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
