[Pg-nuke-devel] Re: pg-Nuke
Brought to you by:
mazzabr
From: Fabio A M. <ma...@al...> - 2003-05-27 03:44:19
|
Ries: I'm sending this message to you AND to pg-nuke-devel list, so we can starting comunicating the right way (with participation of everyone). I have sent to the list our lasts discussions about pg-nuke so most people can understant what is happening through the mailing list history. -------------------- Looking for a better .sig. Suggestions are being accepted. On Mon, 26 May 2003 rv...@dd... wrote: !> !> Ries: !> !> Are you ok if I send three tester to your sample site? !Sure, as long as they don't try to hack the machine.. I haven't done anything !on security the last few months.. ! !> I'm only sorry to tell that unfortunetly SF can't provide us a place !>to !> test our project (they don't support PostgreSQL). ! !But I think that !I can redirect a sub-domain to your site, I'm not sure, but I'll !verify. Do they support PHP4??? If so we can host it on SF and use my !PostgreSQL server as the DB backend. Don't even try to do this. Cross-server database across the internet is too problematic, we'll have problems with response time, speed, CPU load, net traffic, and stability. I can even imagine that SF team won't be happy with such bad utilization of the resouces. I see no problem in using PHP-Nuke to our comunity site, and as soon as we can have a PHP+PostgreSQL server avaiable exclusively for testers I think that we won't have a problem. So, IMO, we can keep things the way they are now. Don't forget, for now we are just a branch, not a fork. ;o) mazza. ! !> !> What do you think? !I think we have a project going on!!! :-) ! !> !> mazza. ! Ries ! !> !> -------------------- !> Looking for a better .sig. Suggestions are being accepted. !> !> On Sun, 25 May 2003 rv...@dd... wrote: !> !> ! !> ! !> !Hey Fabio, !> ! !> !how are you these days? Hopefully your headage didn't stayed to long last !> week. !> ! !> !In the mean time I have added a SQL cach to the code so it releases the !> backend !> !from the SQL calls I make, I also found a little bug in the sql_explode !> !function. Aparently a '' is the escape code for ' in MySQL and I splitted !> the !> !string on such a double quote. I'm currently not sure what happens with !> more !> !quotes.... !> ! !> !It seems the webpages are generated about twice as fast then without the !> cache !> !code. I mode it so that it can use shared memory when available but i !> coulnd't !> !make it to work yet... !> ! !> !Ries !> ! !> !> ! ! ! |