>Surely you must be joking! CachedUpdates? That creates paradox files all
>over the show! Its a nightmare - the ultimate in fat client technology!
>Just imagine, *WHEN* your program crashes, it leaves these MB files in the
>client's hard disk - it soon fills up.
Shurely?! :) I don't know anything about that, Dennis. I've been working
on a project for three months now that uses Cached Updates extensively (and
I'm not happy - it should be using ClientDataSets, but that's another
story). It has certainly crashed multiple times during development, as they
do! I've never bothered clearing up any temporary files left over from
those crashes as my machine has screeds of disk space that I'm not using.
So one might expect that if what you were talking about was a problem, that
there would be a _lot_ of temporary files lying around. But there aren't
any. I scoured my drive, looked in all the likely places, and even looked
at all the files created over the last month and there isn't even one. Have
I really just been extraordinarily lucky?!
>Better to have rich objects, cache the data in your objects, and when the
>user finally hits the save button, call the persist method. This then
>ultimately fires off queries to the backend. With rich objects it is also
>easier to support undos.
Sounds good, but I haven't seen any convincing implementations of it. I
have seen a couple of attempts which turned out to be rubbish, but anything
can be badly done. The case as you put it sounds reasonable, and I'd like
to believe it, but I'm sceptical. If it's really the way to go, isn't there
an unfulfilled market opportunity out there, to produce objects of the type
you describe? So where are they all?
Look, what do all the rest of you use?! If this is the best way to go, let
me know quickly, and I'll change my sinful ways, I promise!!! :)
>Furthermore, keeping queries open with RequestLive, etc., means you need to
>keep more handles open than necessary. With our web server, there is only
>*ONE* database connection, and at most 3 query handles open at any one
time.
One database connection is easy to achieve, but yes, you do end up keeping
multiple open query handles using RequestLive. But that is not at all an
issue when you do things properly using ClientDataSets, and I wish I was...
Cheers,
Carl
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
