Customized SendingQueue

Jan 9, 2013 at 5:43 AM

Hi Kerry.

It's so good to release supersocket 1.5 stable version!
But I have some trouble in using supersocket 1.5.

I was trying to use CircularQueue for SendingQueue because I want to send only lastest N(=capacity of queue) data(s) to session if there are a lot of data to send.

I can redefine the ConcurrentBatchQueue and AppSession's send method on 1.5 beta version,
but it's so hard to make it into circular sending queue in the stable version.

Would you please advise me how to make circular sending queue on 1.5 stable version?
It will be really helpful for me.

 

Thanks.

Coordinator
Jan 9, 2013 at 9:35 AM

Let me think about how to expose the API...

But probably the new enhancement will not be included in 1.5.*

Jan 9, 2013 at 11:15 PM
Edited Jan 10, 2013 at 3:20 AM

I see. 

Thank you for your concern.

 

Lastly I have one more question.

Is the [id #12392] issue on the issue tracker resolved? (TcpAsyncSocketListener stop on "An existing connection was forcibly closed by the remote host")

Actually, I have got this error message in supersocket err.log, and the server started to refuse all the incoming connections after the error occurred.

I compared the TcpAsyncSocketListener.ProcessAccept source of 1.5 beta version source with stable version, but it was same exactly, so I doubt that you did not fix this error to stable version.

 

Please answer to this question and happy new year Kerry!

Coordinator
Jan 10, 2013 at 8:23 AM
Oh, you saved me! You are correct. I'll fix it asap!

Sent from my Windows Phone

From: whitekis
Sent: 1/10/2013 7:15 AM
To: kerry-jiang@hotmail.com
Subject: Re: Customized SendingQueue [SuperSocket:428957]

From: whitekis

I see.

Thank you for your concern.

Lastly I have one more question.

Is the [id #12392] issue on the issue tracker resolved? (TcpAsyncSocketListener stop on "An existing connection was forcibly closed by the remote host")

I compared the TcpAsyncSocketListener.ProcessAccept source of 1.5 beta version source with stable version, but it was same exactly.

Please answer to this question and happy new year Kerry!

Coordinator
Jan 11, 2013 at 3:42 AM

The last commit should fixed this issue.

Jan 11, 2013 at 7:35 AM

Thanks!

But, please forgive to bothering you,

I think it's better that TcpAsyncSocketListener.ProcessAccept method do not execute "OnNewClientAccepted(e.AcceptSocket, null);" when socket error is occured.

(i.e OnNewClientAccepted should be executed only when success to accept)

How about your opinion?

Thank you for your quick fixing.

Coordinator
Jan 11, 2013 at 9:24 AM

Oh, what's a shame...

Thank you for your reminding! Please forgive my buggy code.