SuperSocket Discussions Rss Feed

New Post: Sending Order

kerryjiang — Wed, 19 Jun 2013 16:51:41 GMT

If there are two pieces of data coming from two threads, anyway you cannot ensure the order because you cannot control the CPU scheduler.

If you want to keep the original order of many pieces of data, put your ordered data into a list and then send the list directly:
session.Send(list);

New Post: Do you recommend TLS over SSL3 for SuperSocket?

kerryjiang — Wed, 19 Jun 2013 16:49:39 GMT

Sorry, I have no idea about it.

New Post: Do you recommend TLS over SSL3 for SuperSocket?

eggnog — Mon, 10 Jun 2013 10:11:45 GMT

Do you recommend TLS over SSL3 for SuperSocket? If so, why?

Thank you.

New Post: SSL Socket RENEGOTIATION

faulandcc — Mon, 10 Jun 2013 09:13:49 GMT

Hi eggnog,

no we use to host it on a Windows Server 2008 R2.

Cheers, Alex

New Post: SSL Socket RENEGOTIATION

eggnog — Mon, 10 Jun 2013 06:24:57 GMT

You were hosting with Windows XP?

New Post: Sending Order

eggnog — Sat, 08 Jun 2013 05:01:02 GMT

But are the items always successfully queued in the order that Send(ArraySegment<byte>) is called, and if they do not send immediately, and more requests come, do they ever change order?

I ask this because I have noticed that there is a spin wait which may occur while the data is attempting to queue, and other times the queue itself is replaced.

private void InternalSend(ArraySegment<byte> segment)
{
    if (!m_Connected)
        return;

    //data queued in here
    if (InternalTrySend(segment))
        return;

    var spinWait = new SpinWait();

    while (m_Connected)
    {
        spinWait.SpinOnce();

        if (InternalTrySend(segment))
            return;
    }
}

Isn't it possible that different requesting threads will enter this context, and maybe succeed in queuing in a different order?

Thanks again.

New Post: Sending Order

kerryjiang — Sat, 08 Jun 2013 04:37:38 GMT

Needn't do it. The queue is thread safe, and first queued data must be sent first.

New Post: send size limit

kerryjiang — Sat, 08 Jun 2013 04:36:01 GMT

No limitation.

New Post: send size limit

eggnog — Sat, 08 Jun 2013 02:49:14 GMT

Is there a limit to the number of bytes in the ArraySegment<byte> we pass to AppSession.Send?

If so, what is the limit and how can it be configured?

For example, would this fail?

mySegment = DataSource.GetBytes();  //return 1mb
Assert.Equals(mySegment.Array.Length, 1048576);
myAppSession.Send(mySegment);

New Post: Fast Broadcast

eggnog — Fri, 07 Jun 2013 23:19:49 GMT

Khyalis wrote:

s.SendResponse(message);

Since Khyalis posted this, SendResponse has been deprecated. Instead use Send(ArraySegment<byte> segment)

You could also take a cue from the souce. The following method is in SuperSocket.SocketBase.AppServer<TAppSession, TRequestInfo>

/// <summary>
/// Clears the idle session.
/// </summary>
/// <param name="state">The state.</param>
private void ClearIdleSession(object state)
{
    if (Monitor.TryEnter(state))
    {
        try
        {
            DateTime now = DateTime.Now;
            DateTime timeOut = now.AddSeconds(0 - Config.IdleSessionTimeOut);

            var timeOutSessions = SessionSource.Where(s => s.Value.LastActiveTime <= timeOut).Select(s => s.Value);
            System.Threading.Tasks.Parallel.ForEach(timeOutSessions, s =>
                {
                    if (Logger.IsInfoEnabled)
                        Logger.Info(s, string.Format("The session will be closed for {0} timeout, the session start time: {1}, last active time: {2}!", now.Subtract(s.LastActiveTime).TotalSeconds, s.StartTime, s.LastActiveTime));
                    s.Close(CloseReason.TimeOut);
                });
        }
        catch (Exception e)
        {
            if(Logger.IsErrorEnabled)
                Logger.Error("Clear idle session error!", e);
        }
        finally
        {
            Monitor.Exit(state);
        }
    }
}

It is used to close the sessions, but could just as easily be used to call Send on them.

Also, check out this excellent blog post for other options and explantions as to how the different options (including the above example) effect thread blocking, etc:
Make Async I/O Work For You

New Post: Sending Order

eggnog — Fri, 07 Jun 2013 22:40:31 GMT

Hi kerryjiang

Congratulations on an amazing framework! I have a lot of respect for your work.

I tried to understand the code for sending, but the queuing code is complex and I am not confident.

public class MySession : AppSession<MySession, BinaryRequestInfo>
{
    private readonly _sendLock = new object();
    
    internal void MySend(ArraySegment<byte> data)
    {
        lock (_sendLock)
        {
            Send(data);
        }
    }
}

If MySend is the only way I call Send, is it guaranteed that the segments will be sent in the order that Send is called?

If not, do I need to set Config.SendSync = true?

Thank you very much.

New Post: FTP Server using supersocket

kerryjiang — Thu, 06 Jun 2013 09:06:44 GMT

The default encoding is ASCII, you needn't change it.

New Post: FTP Server using supersocket

chinhnguyen — Thu, 06 Jun 2013 08:55:56 GMT

Hi kerry,
I want use Suppersocket for a FTP server. In FTP, as it is used to send commands to the server and for the server to send responses back to the client, , text based way of sending commands and receiving responses based on TELNET, using the ASCII character set.
I have tested Telnet project in QuickStart. In my project FTP server, i'm using

public FTPServer() : base(new CommandLineReceiveFilterFactory(Encoding.ASCII, new BasicRequestInfoParser(" ", ",")))

I can not get to the data sent from client to Ftp server.

Any ideas what I could be doing wrong?

Thank you!!!

New Post: Dealing with multiple protocols

kerryjiang — Tue, 04 Jun 2013 03:32:52 GMT

Good, you can design a SwitchReceiveFilter to detect protocol, when you find the mark byte, then you should set the NextReceiveFilter of the switch filter with the different protocols' receive filters.

New Post: Dealing with multiple protocols

JetShark — Tue, 04 Jun 2013 03:09:01 GMT

Well, it turned out that I needed to have this done before I could even think about it so I ended up implementing my own Receive Filter, I don't have the code right now but what it does is basically:

if it's protocol "A" then
    myProtocol = "A"
else if it's protocol "B" then
    myProtocol = "B"
...

For instance, one protocol has a fixed header length while another protocol has start/end delimiters, I can differentiate them by checking the first byte of the binary request, then I set a different command key string according to the received protocol, it seems to work just fine.

Thanks for developing SuperSocket!

New Post: Dealing with multiple protocols

kerryjiang — Mon, 03 Jun 2013 02:04:31 GMT

Could you tell me how to choose receive filter in the server side? It is the key to answer your question.

New Post: Dealing with multiple protocols

JetShark — Mon, 03 Jun 2013 00:46:05 GMT

Hi,

I need to implement an UDP server which can handle multiple protocols, these binary requests could have fixed length headers while others could have start/end delimiters, and there could be even more protocols added in the future, these are all sent to the same socket and the protocols are fixed so I can't change them.

So, given a binary stream sent via UDP, I need to be able to "choose" which receive filter will parse it and call its corresponding commands, but I haven't figured out an easy way do this, is there an standard way to do this? or do I have to write my own receive filter?

Thanks in advance!

New Post: How to access AppServer and WebSocketServer

ik606 — Sat, 25 May 2013 13:36:21 GMT

Thank you. That looks like what I need to know.

New Post: How to access AppServer and WebSocketServer

kerryjiang — Sat, 25 May 2013 13:23:14 GMT

http://docs.supersocket.net/v1-5/Multiple-Server-Instances

Please read the last part of this doc.

New Post: How to access AppServer and WebSocketServer

ik606 — Sat, 25 May 2013 02:45:25 GMT

Background:
I have created a program which has 2 services defined, one is inherited from AppServer, and the other is inherited from WebSocketServer.
My program runs as a Windows Service.
The reason for using both SuperSocket and SuperWebSocket is because the SuperWebSocket accepts a connection from an Administrator via Web Browser using WebSockets.
The other clients use a TcpClient, and that connects to the SuperSocket.
I have no problem connecting my Administrator to the SuperWebSocket, and my clients to the SuperSocket.

QUESTION:
In my class, inherited from WebSocketServer, I would like to be able to provide a way for the Administrator to view the Sessions of the AppServer, and send instructions to individual clients.

I am just not sure of the proper way to access the AppServer object. I tried making a temp copy of the AppServer, and accessing the sessions that way. But it never really worked properly. I am new to C# and .NET, but have 15+ years of C++/Unix.

Thank you