Yes, get the latest source code and build it by yourself.
↧
New Post: SuperWebSocket.dll to use with SuperSocket 1.6.3
↧
New Post: How to deploy LiveWebChat example?
How I go to the error log?
↧
↧
New Post: How to deploy LiveWebChat example?
↧
New Post: node.js
No, SuperWebSocket is a server.
↧
New Post: Has anyone got trySend to work ?
Hi,
I'm trying to use SuperWebSocket.
I'm finding that when I use trySend for binary data, it returns true, but the other end never receives the data.
When I replace the trySend with a plain send, it works fine, except that it now has the potential to block when used on a low bandwidth connection.
What is the right way to use trySend ? Is there some runMessagePump or serviceSocket thing I will need to call to make it actually send the data out ?
Here's the snippet of code: (payload is a byte array with about 100 bytes)
//doesnt work:
bSent = wsSession.TrySend(payload, 0, payload.Length);
works:
wsSession.Send(payload, 0, payload.Length);
I'm trying this out on Windows 7, though, my final target is mono. I had originally the package from nuget, but I have now tried replacing the dlls from the binaries I just downloaded from the codeplex site. The trySend still does not work.
Any ideas will be appreciated.
I'm trying to use SuperWebSocket.
I'm finding that when I use trySend for binary data, it returns true, but the other end never receives the data.
When I replace the trySend with a plain send, it works fine, except that it now has the potential to block when used on a low bandwidth connection.
What is the right way to use trySend ? Is there some runMessagePump or serviceSocket thing I will need to call to make it actually send the data out ?
Here's the snippet of code: (payload is a byte array with about 100 bytes)
//doesnt work:
bSent = wsSession.TrySend(payload, 0, payload.Length);
works:
wsSession.Send(payload, 0, payload.Length);
I'm trying this out on Windows 7, though, my final target is mono. I had originally the package from nuget, but I have now tried replacing the dlls from the binaries I just downloaded from the codeplex site. The trySend still does not work.
Any ideas will be appreciated.
↧
↧
New Post: Has anyone got trySend to work ?
Which client are you using? And which API of it are you using?
↧
New Post: Has anyone got trySend to work ?
Oops.
Looks like when I downloaded the new version and replaced my earlier nuget versions with the downloaded version, I had not realized that the namespaces had changed.
I went ahead and changed the namespaces now and it seems to work. I have not yet tested with a low bandwidth condition where trySend will return false, but atleast now, when it returns true, the data is coming over to the other side.
Kerry, thank you for the fast response.
I was using the superwebsocket .net library from nuget as a client.
Looks like when I downloaded the new version and replaced my earlier nuget versions with the downloaded version, I had not realized that the namespaces had changed.
I went ahead and changed the namespaces now and it seems to work. I have not yet tested with a low bandwidth condition where trySend will return false, but atleast now, when it returns true, the data is coming over to the other side.
Kerry, thank you for the fast response.
I was using the superwebsocket .net library from nuget as a client.
↧
New Post: Has anyone got trySend to work ?
Did you misunderstand something?
The SuperWebSocket is the websocket server not a client.
The SuperWebSocket is the websocket server not a client.
↧
New Post: Has anyone got trySend to work ?
I meant to say I'm using WebSocket4Net from nuget as a client for testing from windows. You are right. superwebsocket is the server code and not used in the client.
Ultimately, the server is going to be running on mono and the actual clients will be c++ clients using libwebsockets.
Anyway, it seems to be working now.
The one thing I've not been able to do is to send data larger than about 10k bytes without causing a protocol error on the server. I've not found a way to send larger packets with WebSocket4Net. It only seems to allow me to change the receive buffer size and not the send buffer size. So, for now, I've limited the frame size to about 9k bytes. I would have liked to have upto 64k.
But in any case, I'm glad to have your .net libraries to work with. Thank you so much for contributing to open source.
Ultimately, the server is going to be running on mono and the actual clients will be c++ clients using libwebsockets.
Anyway, it seems to be working now.
The one thing I've not been able to do is to send data larger than about 10k bytes without causing a protocol error on the server. I've not found a way to send larger packets with WebSocket4Net. It only seems to allow me to change the receive buffer size and not the send buffer size. So, for now, I've limited the frame size to about 9k bytes. I would have liked to have upto 64k.
But in any case, I'm glad to have your .net libraries to work with. Thank you so much for contributing to open source.
↧
↧
New Post: 3G Problem not yet solved
Dear ALL ;
I wrote a superwebsocket Console Application on the server side and I use jquery connection from the client side , I was working fine until I disconnect the Wifi and I conected it by 3G , that is not websocket issue , its the telecom Provider issue I think , But i believe there is way out .
So kindly advice me what steps should I follow to get it work over 3G and 4G connection.
Regards...
I wrote a superwebsocket Console Application on the server side and I use jquery connection from the client side , I was working fine until I disconnect the Wifi and I conected it by 3G , that is not websocket issue , its the telecom Provider issue I think , But i believe there is way out .
So kindly advice me what steps should I follow to get it work over 3G and 4G connection.
Regards...
↧
New Post: 3G Problem not yet solved
Hello,
We were experiencing this exact issue, try connecting over ssl - the websocket works perfect for us over ssl.
Regards,
Simon
We were experiencing this exact issue, try connecting over ssl - the websocket works perfect for us over ssl.
Regards,
Simon
↧
New Post: SuperWebsocket With 3G Problem
Replied on your other thread https://superwebsocket.codeplex.com/discussions/562005
↧
Commented Unassigned: GetAllSessions() returns null session [12414]
I am getting null session object in GetAllSessions() method.
It is not a frequent issue. Most of the time it happens when this method is called just before a new session is connected or just after an existing session is closed.
Thanks in advance!!!
Comments: This happens to me also. Same stack trace, same situation. Any solution? Using version 0.8 from Nuget.
It is not a frequent issue. Most of the time it happens when this method is called just before a new session is connected or just after an existing session is closed.
Thanks in advance!!!
Comments: This happens to me also. Same stack trace, same situation. Any solution? Using version 0.8 from Nuget.
↧
↧
New Post: Concurrent connection issue
When I try to have 100 client concurrent connecting to the server. The client will get the refuse connection error message. Is it any setting in server to adjust the max. concurrent connection figure?
↧
New Post: SuperWebSocket.WebSocketSession.Send(...) method - sync or async?
Hello,
I looked through many discussions and could not find the answer:
if SuperWebSocket.WebSocketSession.Send(string message) method works synchronously or asynchronously?
Are there different methods (or mode configuration) for sending in synchronous or asynchronous mode?
I see that 'SocketMode.Async' mode (that was mentioned in some older discussions) does not exist anymore, there are only 'Tcp' and 'Udp' values.
I'm using the latest sources of SuperWebSocket (project version 0.9) with SuperSocket 1.6.3
Thanks
Yuri
I looked through many discussions and could not find the answer:
if SuperWebSocket.WebSocketSession.Send(string message) method works synchronously or asynchronously?
Are there different methods (or mode configuration) for sending in synchronous or asynchronous mode?
I see that 'SocketMode.Async' mode (that was mentioned in some older discussions) does not exist anymore, there are only 'Tcp' and 'Udp' values.
I'm using the latest sources of SuperWebSocket (project version 0.9) with SuperSocket 1.6.3
Thanks
Yuri
↧
New Post: SuperWebSocket.WebSocketSession.Send(...) method - sync or async?
Yes, it is asynchronously
↧
New Post: Concurrent connection issue
↧
↧
Commented Unassigned: GetAllSessions() returns null session [12414]
I am getting null session object in GetAllSessions() method.
It is not a frequent issue. Most of the time it happens when this method is called just before a new session is connected or just after an existing session is closed.
Thanks in advance!!!
Comments: Could you use the latest source code of the repository?
It is not a frequent issue. Most of the time it happens when this method is called just before a new session is connected or just after an existing session is closed.
Thanks in advance!!!
Comments: Could you use the latest source code of the repository?
↧
New Post: SuperWebSocket.WebSocketSession.Send(...) method - sync or async?
But if the sending queue is full, the sending will become synchronous.
↧
New Post: Optimal Size - SendingQueueSize for high count transmissions
Hi Kerry,
I'm building a publish subscribe system which has a minimum 1000 active clients subscribing to event broadcast.
I have been doing load testing and noticed since I upgrade recently to SuperSocket 1.5+ (currently using 1.6.3), I noticed it couldn't handle a lot of broadcasts - it would be very slow once I flood the session with events.
After playing around, I increase the sendingQueueSize to 1000 (Default = 5), it seems to make it, but sometimes, I can still see sometimes, the session.Send to lock (supposedly async sending, am I correct?)
Could you explain how the SendingQueue works? I believe, I read on another thread, when sending queue is full, it become synchronous.
So, I'm thinking possibly, setting the sendingQueueSize to a large number, but, not sure what would be the issue beside more RAM?
Thank you very much
I'm building a publish subscribe system which has a minimum 1000 active clients subscribing to event broadcast.
I have been doing load testing and noticed since I upgrade recently to SuperSocket 1.5+ (currently using 1.6.3), I noticed it couldn't handle a lot of broadcasts - it would be very slow once I flood the session with events.
After playing around, I increase the sendingQueueSize to 1000 (Default = 5), it seems to make it, but sometimes, I can still see sometimes, the session.Send to lock (supposedly async sending, am I correct?)
Could you explain how the SendingQueue works? I believe, I read on another thread, when sending queue is full, it become synchronous.
So, I'm thinking possibly, setting the sendingQueueSize to a large number, but, not sure what would be the issue beside more RAM?
Thank you very much
↧