et-nik / phpwebsocket

Automatically exported from code.google.com/p/phpwebsocket
0 stars 0 forks source link

Server refuses new client after closing original #1

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
If i connect with Chrome, everything is fine till i close chrome or
disconnect.. If i try reconnecting, the connection is immediately closed?

Nice work by the way.

Original issue reported on code.google.com by terrybro...@gmail.com on 15 Dec 2009 at 10:56

GoogleCodeExporter commented 8 years ago
I get the same problem. Why does this happen?

Original comment by joshda...@gmail.com on 21 Dec 2009 at 1:25

GoogleCodeExporter commented 8 years ago
Me thinks it has something to do with the storing of handshakes per socket.. 
part of
his "todo" list

Original comment by terrybro...@gmail.com on 21 Dec 2009 at 9:48

GoogleCodeExporter commented 8 years ago
Hey,

i have implemented the ability to handle multiple request.
one or two more days and i will post a more complex version of this server.
but there are many things that must be figured out...

--mo

i hope my english isnt to bad, im from germany

Original comment by moritzw...@gmail.com on 22 Dec 2009 at 11:39

GoogleCodeExporter commented 8 years ago
Sounds great. Keep up the good work.

Original comment by terrybro...@gmail.com on 22 Dec 2009 at 4:58

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
Maybe I don't see something, but the problem still exists.

I've changed the $handshake variable to an array, which contain existing 
sockets. 
Actually, it duplicates $allsockets, but they have different moments of 
initiallization. The 
main idea - we do a handshake whenever a new socket is being opened. In other 
words we do it 
when there's no socket in the array yet. So it handles multiple connections (at 
least, the 
problem is solved)..

Hope it'll be helpfull for anyone.

Original comment by sidelnik...@gmail.com on 25 Dec 2009 at 8:54

Attachments:

GoogleCodeExporter commented 8 years ago
2010.02.16 - Fixed

Original comment by georgen...@gmail.com on 16 Feb 2010 at 7:01