Tony,
Have a look at the MS URL that Kerry posted - it's a pretty good argument
for the flying objects scenario - although the MS argument is angled
towards being able to connect to any data storage mechanism (including
cheap shot at IBM with a Universal Data Access vs Universal Database
strategy) it puts the case for handling data via multiple small objects and
a reasonable level of indirection. Also has some stuff that sparked my
interest in remote data via HTTP if ADO Express will do it.
Max
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Tony Blomfield
Sent: Monday, 6 September 1999 21:05
To: Multiple recipients of list delphi
Subject: Re: [DUG]: Thin Database Components.
Thanks Max. I'm already into that, and more or less decided it is the most
efficient all round solution. Less work to implement as well.
I was really probing to find out what others are up to in an endeavor to
broaden my horizons a little.
I'm not at all sure about the flying objects scenario. When you get down to
the nitty gritty its hard to imagine how this can result in lower average
network traffic.
I can see that using interfaces results in a more elegant solution, and
offers the opportunity to use patterns, but once again, just like removing
the BDE, I don't see why the hell this should be a design goal in its own
right.
Seems I'm missing the plot with so many telling me I should get into flying
objects. I took a look at this stuff a cupla years ago and wasn't taken
with
it. Guess I better take another look and get educated. Ah but how? If you
aint in the in club, then its pretty hard to get to know it.
Kerry writes a pretty compelling argument. The least I can do is take a
closer look at it all.
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
