Re: what is going on with gtk.php.net?

On Thu, 2004-07-22 at 17:43, Richard Thomas wrote: > Such a "hack" doesn't seem like it would scale very well at all. It > seems to me you would be better off with a diffrent form of > communication between the applications, like possibly a tcp connection. I can't agree that this is a hack and it scales very well. I use this methds in an application that dispatches goods from a warehouse. It is used by 30 - 40 simultainous users spread over 4 georaphic locations. It handles 30,000 transactions a day and since it went live has handeled close to 3 million transactions. Our database servers average 15,000 queries a second and do not even flinch so a couple of extra queries to make sure that the databsae handle is still alive is a tiny overhead. > A good example.. Large company address book, employees work 9-5, so a > majority of your "initial" activity would occur between 8:55-9:00. 1000 > employees connecting to the db and performing a query to load there > address books for the data, then every time the address book changes > each one has to reperform the query. > It sounds to me like your saying you load the whole address book into memory? In real life you perform one query to connect to the database when you start the database and another when you want to look up an address, then another when you want another address, not a big issue for any database. > Instead using some tcp setup it would happen more streamlined. > 1. People connect, First person that makes request causes query, Final > dataset built, cached and then sent. I also use a tcp server in the same application,but there are times you need real-time which is far more suitable for a database. > 2. Everyone else pulls a simple dataset out of the tcp server memory, > low overhead. Then when someone updates an address, everyones local copy has to be updated. What happens if 2 people try to update the same record at the same time. Lots of code to handle that, or your database will do it all for you. > 3. Ability to send "broadcasts" over the tcp connection letting people > know there are updates to the address book. Instead of everyone pooling > the server now you have told everyone there is a update, Next time they > open there address book it will pull it. so if you have 50,000 records in the datasset thats quite a lot of ram used just to hold the data that you may never use. > Tony > tony@php.net wrote: > > On Thu, 2004-07-22 at 09:11, Anders K. Madsen wrote: > > > >>On Thu, 22 Jul 2004 12:57:46 +0700 (SE Asia Standard Time) > >>xaviero1412@yahoo.com.au (Xaviero) wrote: > >> > >> > >>> so, tony, could u write some article bout php-gtk that explain how to > >>> build > >>>an application such like address book that connect to mysql server ? > > > > > > I'm working on one at the moment :) > > > > > >>Well, PHP-GTK is just an extension of PHP, so any PHP/MySQL tutorial > >>would do in your case. > > > > > > Almost, however you need to be aware that a gtk app is likely to be open > > on someones desktop all day, and may only be used for a few minutes at a > > time. When you come back to it your db handle has gone stale. I always > > extend my basic db class with a gtk specific one that checks the > > connection is alive before I use it. > > > > tony > > > > > -- > Richard Thomas > Cyberlot Technologies Group Inc. > 507.398.4124 - Voice