Questions and bugs

wave84

posted Feb 1 '13 at 11:49 am

So I have upgraded freichat to version 8 on my server (custom install, not without issues) and adjusted many functions according to my needs. I added user pictures to the chatroom, modified database design a bit, etc.
The code is generally nice but I have a few questions:

1. First of all, there is a nasty bug in the install which fails right at the start saying that "arg.php is not writeable" (although it is). After spending 20 minutes banging my head against the wall checking permissions, I checked the freichat code and noticed it is "hardcode.php" that actually needs to be writeable. So you need to adjust the message there.

2. Secondly, why did you choose to revert to MyISAM, especially now in the days of Mysql 5.5 when InnoDB is the default and is clearly superior in every way (even more so for a chat application)?

3. Third, are you sure it's worth using persistent connections? Most users might run into issues because of this, if they don't know how to adjust their "max_connections" variable in my.cnf. And the performance benefits are neglijible, especially if the sql server resides on the same machine as the web server (as probably most of your users do). In my case, a few minutes after launching the chat on the live server, I ran into a "Failed to conect to SQL server; Too many connections" error. Luckily I knew immediately how to fix it.

That's it for now; more feedback coming :)

So I have upgraded freichat to version 8 on my server (custom install, not without issues) and adjusted many functions according to my needs. I added user pictures to the chatroom, modified database design a bit, etc. The code is generally nice but I have a few questions: 1. First of all, there is a nasty bug in the install which fails right at the start saying that "arg.php is not writeable" (although it is). After spending 20 minutes banging my head against the wall checking permissions, I checked the freichat code and noticed it is "hardcode.php" that actually needs to be writeable. So you need to adjust the message there. 2. Secondly, why did you choose to revert to MyISAM, especially now in the days of Mysql 5.5 when InnoDB is the default and is clearly superior in every way (even more so for a chat application)? 3. Third, are you sure it's worth using persistent connections? Most users might run into issues because of this, if they don't know how to adjust their "max_connections" variable in my.cnf. And the performance benefits are neglijible, especially if the sql server resides on the same machine as the web server (as probably most of your users do). In my case, a few minutes after launching the chat on the live server, I ran into a "Failed to conect to SQL server; Too many connections" error. Luckily I knew immediately how to fix it. That's it for now; more feedback coming :)

admin

posted Feb 1 '13 at 5:50 pm

1. First of all, there is a nasty bug in the install which fails right at the start saying that "arg.php is not writeable" (although it is). After spending 20 minutes banging my head against the wall checking permissions, I checked the freichat code and noticed it is "hardcode.php" that actually needs to be writeable. So you need to adjust the message there.

Thanks for reporting this , we failed to notice it.

2. Secondly, why did you choose to revert to MyISAM, especially now in the days of Mysql 5.5 when InnoDB is the default and is clearly superior in every way (even more so for a chat application)?

Because when we were installing freichat in many servers , we found some of them didn't support InnoDB .

3. Third, are you sure it's worth using persistent connections? Most users might run into issues because of this, if they don't know how to adjust their "max_connections" variable in my.cnf. And the performance benefits are neglijible, especially if the sql server resides on the same machine as the web server (as probably most of your users do). In my case, a few minutes after launching the chat on the live server, I ran into a "Failed to conect to SQL server; Too many connections" error. Luckily I knew immediately how to fix it.

I guess you are right about persistent connections .The upcoming versions of FreiChat will have an event based model . We will get rid of persistent connections (or make it optional through the backend)
in this version.

&lt;blockquote&gt;1. First of all, there is a nasty bug in the install which fails right at the start saying that "arg.php is not writeable" (although it is). After spending 20 minutes banging my head against the wall checking permissions, I checked the freichat code and noticed it is "hardcode.php" that actually needs to be writeable. So you need to adjust the message there.&lt;/blockquote&gt; Thanks for reporting this , we failed to notice it. &lt;blockquote&gt;2. Secondly, why did you choose to revert to MyISAM, especially now in the days of Mysql 5.5 when InnoDB is the default and is clearly superior in every way (even more so for a chat application)?&lt;/blockquote&gt; Because when we were installing freichat in many servers , we found some of them didn't support InnoDB . &lt;blockquote&gt;3. Third, are you sure it's worth using persistent connections? Most users might run into issues because of this, if they don't know how to adjust their "max_connections" variable in my.cnf. And the performance benefits are neglijible, especially if the sql server resides on the same machine as the web server (as probably most of your users do). In my case, a few minutes after launching the chat on the live server, I ran into a "Failed to conect to SQL server; Too many connections" error. Luckily I knew immediately how to fix it.&lt;/blockquote&gt; I guess you are right about persistent connections .The upcoming versions of FreiChat will have an event based model . We will get rid of persistent connections (or make it optional through the backend) in this version.

Necessity is the mother of all inventions!

Pending draft

Confirm move posts

Insufficient permissions

Select a different topic

Edit history