Thread Per Client/Request? RRS feed

  • Question

  • Hi.

    I must create a server client architecture which holds a live connection between them. For responsiveness should i make 1 thread per client connect? What about when i have 100 clients connected simultaneous won't 100 threads be to much? 
    Me http://www.zapacila.com
    Monday, June 29, 2009 6:25 PM

All replies

  • It entirely depends on number of processors available and architecture you chooses. In case you are bound only to vertical scalability - you can use such frameworks as Concurrency and Coordination Runtime.
    Vitaliy Liptchinsky http://dotnetframeworkplanet.blogspot.com/
    Tuesday, June 30, 2009 8:33 AM
  • What is the application?
    What is the network connection?
    What data is being sent across the connection?
    How often is data really required to be sent across the connection - can you work in an 'offline' mode, and sync up at the end of the session, or when the user clicks save?

    So long as you don't hold the connection open, and close and re-establish the connection, there shouldn't be too many scalability issues.

    Please give a little more information if you can.


    MCSD, MCTS, MCPD. Please mark my post as helpful if you find the information good!
    Thursday, July 2, 2009 5:45 AM
  • Hey Martin,

    It seems that all that i wanted to accomplish is already done by WCF.

    I needed multiple clients - 1 server for an ERP.

    Me http://www.zapacila.com
    Thursday, July 2, 2009 9:39 AM