Does anyone want to help my team work on a private bittorrent tracker project?
http://stdev.cvs.sourceforge.net/stdev/0.1/
Uses PHP4 OOP and (eventually) XML-RPC - Am looking for someone to work on more modules, suggestions to enhance security and lightweightedness, and possibly a C-based tracker that conforms to STDev's SQL structure - AIM me Ersan181
I can't be of a bigtime help but if you have any questions design wise we could share notes sometime.
Need to establish some sort of flexible CSS structure to be used for themes.
Why not use smarty for theming? It allows you to seperate program code from design code and you wouldn't be limited to a potentially strict structure.
Smarty uses WAY too many resources.
Quote from: Ersan on May 23, 2006, 05:33:47 PM
Smarty uses WAY too many resources.
Provide figures. I stand unconvinced that Smarty uses way too "many" resources. ;)
Quote* Now talking on #stdev
* reliant.p2p-irc.net sets mode +n #stdev
* reliant.p2p-irc.net sets mode +t #stdev
I am disappointed. :(
I frequent P2P-IRC (#linux, #rockbox, #kerrazy-torrents) and I haven't even heard of you guys. :(
Try #supertorrents
Quote from: Sidoh on May 23, 2006, 08:47:30 PM
Provide figures. I stand unconvinced that Smarty uses way too "many" resources. ;)
I couldn't find any studies or whatnot done on it but as far as theory goes, caching the smarty requests to the harddrive (as smarty does) makes the application more IO dependant, which is one of the bigger problems with the current system.
I'm trying to make it as lightweight (but feature-rich) as possible.
Maybe it's all in my head, smarty = rails, and I hate rails. I also don't see the need for a ginormous chunk of code devoted to aspects of templating that I'll never need.
Caching the compiled templates greatly reduces execution time, from what I understand. If smarty didn't do that, it would take much longer per request to do the same thing.