C#

private int m_Value;
pubilc string Text
{
    get
    {
        int result = Value;
        // Recalculate if needed here - ToDo
        return string.Format("your format", result);
    }
    set
    {
        // Validate/Strip here - ToDo
        int result;
        int.TryParse(value, out result);
        Value = result;
    }
}
public int Value
{
    get { return m_Value; }
    set
    {
        m_Value = value;
        // Raise event here - ToDo
    }
}

Bala K wrote:

The fact is u cant understand the question...

Bala K wrote:

Assume 3 or 5 textbox which will be filled by user at runtime (v dont know how many he will fill)
and these values should assigned to radio button text which will be created dynamically.

string BuildRadioText()
{
    StringBuilder textBuilder = new StringBuilder();
    foreach (Control control in Controls)
    {
        if (control is TextBox)
            if (Text.Length > 0)
            {
                if (textBuilder.Length > 0)
                    textBuilder.Append(", ");
                textBuilder.Append(control.Text);
            }
    }
    return textBuilder.ToString();
}

RadioButton dynamicRadio = new RadioButton();
dynamicRadio.Text = BuildRadioText();
Controls.Add(dynamicRadio);

Metal76 wrote:

1) Suppose you have several clients connected. Do all the callbacks (OnClientConnect, OnClientRead...) "live" in the same thread? That is, while I'm inside OnClientRead to serve one of the clients, can my code be interrupted by an OnClientRead from another client?

I performed a simple investigation, and it seems that OnClientRead for different clients are called from the same thread. So, it seems that OnClientRead execution never gets interrupted. Am I right? Is this always true? If so, I think I can safely remove all the lock statements for clientList access.

Metal76 wrote:

2) Is it correct to always launch a new AsyncCallback every time? e.g. new AsyncCallback(OnClientRead) inside OnClientRead. Does this waste resources? Should I keep a different AsyncCallback for each client and reuse it?

----------------------------------
Be excellent to each other

Nick Butler wrote:

Just as a matter of style, I would put the calls to BeginAccept and BeginReceive in a private method each, just so you don't have two copies of each call.

private void StartReceiving(ClientState clientState)
{
    clientSocket.BeginReceive(clientState.Buffer, 
                              0,
                              clientState.Buffer.Length, 
                              SocketFlags.None,
                              new AsyncCallback(OnClientRead),
                              clientState);
}

Metal76 wrote:

Do you mean something like the following?

Metal76 wrote:

1) Which is the correct way to gracefully shutdown the server app? I know for sure that I have to close all the client sockets; are there any other resources to shutdown in the async pattern I'm following?

Metal76 wrote:

So, it seems to me that keeping a clientList is only useful when I want to shutdown the server (so that I can dispose of each client socket) and if I want to offer to the users of my class the possibility to perform actions on connected clients (e.g. check state of client A, forcibly shutdown connection with client B etc.).

Is this right?

----------------------------------
Be excellent to each other