Fastest way to get thousands of db records to client in 3 tier?

John J. Lee jjl at pobox.com
Wed Sep 24 13:22:30 EDT 2003


amonroejj at yahoo.com (R. Alan Monroe) writes:

> In article <3f71361f$0$97182$edfadb0f at dread12.news.tele.dk>, Max M <maxm at mxm.dk> wrote:
> 
> >> I intend to write both client and server in Python, and my main goal 
> >> in the first cut is speed. Suggestions?
> 
> >Why do you need thousand of rows at the client? Normally you would get 
> >the results in batches, so that you only transfer at most a few hundred 
> >at a time to the client.
> 
> Those types of tests will be done in my second cut.

At this stage you should be worrying more about this than about the
details of the protocol and implementation thereof.


> >Why not let the client ask directly if it is faster?
> 
> I thought that defeats the purpose of having 3 tiers. You'd have to 
> update the client if/every time business rules changed. Unless I'm 
[...]

Why?  The client asks the client in terms of "business logic", the
server asks the database in SQL.  If server and DB can communicate
quickly, no problem.


John




More information about the Python-list mailing list