search

hijera / client175

Automatically exported from code.google.com/p/client175
GNU General Public License v3.0
0 stars 0 forks source link

Client175 blocks access to other MPD client #37

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
I have Client175 setup behind an Apache server.  After accessing the Client175 
web interface, I'm no longer able to connect to MPD from other client. It looks 
like Client175 has exclusive access to MPD until I stop my Apache server.

Is this a known behavior?  Is there anything I can do to prevent this?

Thanks!

Original issue reported on code.google.com by jf1.clou...@gmail.com on 28 Jul 2011 at 2:15

GoogleCodeExporter commented 9 years ago 
That should not happen at all.  Client 175 will open a single telnet session 
and keep it open.  I would check your mpd.conf file and look at how many 
connections are allowed.  

It could be that the connection limit is set one, which would work for many 
other clients that periodically poll for status updates and then close the 
connection.  This client takes advantage of the idle feature to respond 
instantly to events, which means the connection it opens is never closed.

Original comment by cseic...@gmail.com on 30 Jul 2011 at 6:57

GoogleCodeExporter commented 9 years ago 
Hi,

after changing the number of allowed connections to 20 in MPD I don't have the 
issue anymore.  But I think there is still an issue with the software.  As soon 
as I start apache and I navigate to my installation base I see 10+ connections 
established to MPD from the client175 (I don't have any other MPD client 
installed on this computer).  Any idea why I'm seeing that much connections?

Thanks!

Original comment by jf1.clou...@gmail.com on 1 Aug 2011 at 1:17

GoogleCodeExporter commented 9 years ago 
I didn't think about this initially, but when run behind apache each individual 
thread has to have it's own mpd connection, because there is no central 
controller to share it with.  It would work best if it was not run behind 
Apache.

For people that have an existing Apache install that don't want to use another 
port, I think it would be best to use apache as a proxy for the built-in python 
server rather than using mod_python to run the app within apache.  I'll just 
need to figure out what the setup is.

Original comment by cseic...@gmail.com on 7 Aug 2011 at 12:26