[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] low Performance

From: Karsten Hilbert
Subject: Re: [Gnumed-devel] low Performance
Date: Mon, 7 Jun 2004 00:26:41 +0200
User-agent: Mutt/

> > Ideally, all DB communication should be done by a background thread, so the
> > user can start typing notes etc. while stuff is loading. I'm not sure about
> > the best way to implement this yet.
> This is what we have asynchronous backend communication for.
That's news to me.

> 1.) a complex / time consuming query is initiated asynchronously on the server
How do I do that? Particularly with the DB API? Specifically?

> 2.) when ready, the server notifies the client that he can fetch the data now
Again, how is that done a) specifically, b) with the DB API ?

> 3.) Ideally, we'll have a xml-rpc service or similar on the backend that 
> pre-processes all data on the server in exactly the way the client wants it, 
> and delivers that data then. Despite the xml overhead we can still archive 
> less network traffic and better performance that way. We could even get rid 
> of the pypgsql dependency (and mxDateTime dependency) on the client side that 
> way.
Surely so. Again, ideally. Maybe this shows that we shouldn't
spend all *too* much effort on optimization in 0.1 ? Just a

GPG key ID E4071346 @
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

reply via email to

[Prev in Thread] Current Thread [Next in Thread]