I realize that with the announcement of the PHP port there will probably be questions regarding this. So, instead of cluttering up the other forums I figured I would create a new board just for comments/questions regarding this.

---
Scream
<A HREF="http://www.wcsoft.net" target="_new">http://www.wcsoft.net</A>

uhm.....

whoooo hoooo!!!!!!

--------------
your ad here! adspace@extremeforums.org
<A HREF="http://www.extremeforums.org" target="_new">http://www.extremeforums.org</A>

Thank you Scream!!!!

Do you have a guestimation on how long until beta ?

Will

Do you know who's working on the conversion, WWWThreads people or ? Is there a way to have it done faster ($$$)? Can I help?

Erm....Scream is WWWThreads people . And seeing as how it's his program, I think it's him who's doing it.
Strange thing is, I actually wondered about the PHP version this morning, and then voila! he's already working on it.
I know PHP is the latest and greatest thing, Scream, but what advantages can it give us over Perl, except for the fact that some people just want or only have PHP? (Which is very hard to believe in this day and age)

At this point I would hate to even take a guess on a timeline. Just keep watching the changelog. I'll post the url to the development site once I get a little further along.

---
Scream
<A HREF="http://www.wcsoft.net" target="_new">http://www.wcsoft.net</A>

LoneVVolf is correct. WWWThreads people is me;). Converting actually has been going pretty smooth, much faster than I had originally thought anyways. In a couple hours yesterday I got about 5 scripts ported over.

---
Scream
<A HREF="http://www.wcsoft.net" target="_new">http://www.wcsoft.net</A>

I'll admit that my knowledge in PHP is limited, but from what I can tell it is a pretty easy language to work with. The main benefit is that PHP is a server module, so unlike perl it doesn't have to fire up a seperate process to compile the script and execute it. So, speed is a big factor.

I'll probably have more opinions about it in the near future. And someone else might be able to give a better answer on the benefits.

---
Scream
<A HREF="http://www.wcsoft.net" target="_new">http://www.wcsoft.net</A>

Let me give you a good example of why it's good to use PHP..

The forum I use to run got so many hits that it crashed constantly.. It was mostly because sooo many instances of perl executing that my machine would slow way down and the db couldn't handle it etc..

PHP only has one instance, it runs from the server level.. So it keeps things speedy and crashes less on an active forum.. (That means 100 hits at once, doesn't cause perl to run 100 times on your server, executing the same file..)

Also I think PHP can keep a persistent connection to the db where as Perl can't (Maybe mod_perl?) which cuts down on all of the db activity..

I still think Perl is a lot more fun to develop in though.. Especially when you start doing OO stuff (adds some spice to the same old boring Perl stuff) =)

Jeremy 'PeelBoy' Amberg

Ok, I'm not getting it.

PHP has an apache module - mod_php.
Perl has an apache module - mod_perl.

Neither require spawning external processes to byte compile the scripts. They are read in once at init, and you go.

The apache benchmarking tool has shown WWWThreads 4.4.1 capable of handline 100 page requests/second of wwwthreads.pl w/3 categories and 20 forums on a 360 Mhz Solaris 2.7 machine running apache 1.3.9 and mod_perl.

This can be scaled up fairly quickly using a seperate machine for the MySQL server from the web server and using a non DNS based load balancer.

Don't get me wrong, PHP has it uses. I looked at using a number of PHP boards before settling on WWWthreads last year. WWWThreads was by far the superior solution. It had the richest feature set provided and the cleanest UI PLUS its backed by MySQL. For the life of me I can't figure out why so many sites use UBB...

I question your rationale of claiming that WWW threads needs to be ported for speed considerations.