[isf-wifidog] Thoughts on implementing an ORM in WifiDog

Ian White ian.white at datamile-computers.com
Lun 22 Mai 09:33:57 EDT 2006

I've used smarty for some of my apps, but developed a blocking 
template system to enable performance increases



This is showing the main page, and 4 blocks. The main page makes

«insert name="viewitem_block" script="viewitem_block.php"»  type calls

Each of these blocks are running there own smarty cache, so pretty 
static pages are every 30 mins etc, and on other pages the cache only 
clears when new data is added. This cuts down on a great number of 
queries etc.


> I really think that in order to provide a scalable and lightweight  
> solution, we will absolutely need to implement a good open source 
> solution in Wifidog (realistically I think we'll start doing it 
> v1.0, since it's a very critical change in the core).
> Why ? Simply because if you analyze the flow on many pages (take  
> hotspot_status.php for example) we generate dozens of SQL queries  
> each time, not mentionning that we could as of now use persistent  
> connections to postgresql... (i think I'll investigate it today).  
> Simply to display the hotspot status there will be a ton of exactly  
> identical queries (like node->getNetwork() ) . Since we do not have  
> any cache, these eat much resources. Also, managing the ORM is such 
> pain in the ass now... There are a few very very good ORM solutions  
> for PHP5 now, almost as good as Hibernate (in the J2EE community).
> Take these 2 examples :
>    - Doctrine : http://www.phpdoctrine.com/
>    - Propel : http://propel.phpdb.org/trac/
> These are the most actively developped ORM solutions now.
> Doctrine looks very interesting :
> http://www.phpdoctrine.com/comparison.php
> more food for thought...


More information about the WiFiDog mailing list