Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. .NET (Core and Framework)
  4. application server implementation

application server implementation

Scheduled Pinned Locked Moved .NET (Core and Framework)
databasesysadminwindows-adminsecuritybusiness
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R Offline
    R Offline
    Ryan Minor
    wrote on last edited by
    #1

    Hi there Wondering generally how the server side of an application server is done (non web based). Say you wanted to write an accounting program. The server would run on Windows Server 2008 for example and handle business logic and database access. The client program would have the client forms, etc and obtain data from the server. Is the server software usually set up as a Windows service normally? It would listen on certain ports? How does the server handle multiple concurrent users? I would imagine that after authentication, some sort of thread is created to listen for requests from the user?

    L 1 Reply Last reply
    0
    • R Ryan Minor

      Hi there Wondering generally how the server side of an application server is done (non web based). Say you wanted to write an accounting program. The server would run on Windows Server 2008 for example and handle business logic and database access. The client program would have the client forms, etc and obtain data from the server. Is the server software usually set up as a Windows service normally? It would listen on certain ports? How does the server handle multiple concurrent users? I would imagine that after authentication, some sort of thread is created to listen for requests from the user?

      L Offline
      L Offline
      Lost User
      wrote on last edited by
      #2

      Ryan Minor wrote:

      Say you wanted to write an accounting program. The server would run on Windows Server 2008 for example and handle business logic and database access. The client program would have the client forms, etc and obtain data from the server.

      I'd try to check if a database-server would suffice :)

      Ryan Minor wrote:

      Is the server software usually set up as a Windows service normally?

      Yup, that way it starts when the machine starts, without the Admin even having to log in.

      Ryan Minor wrote:

      It would listen on certain ports?

      Any free port will do.

      Ryan Minor wrote:

      How does the server handle multiple concurrent users? I would imagine that after authentication, some sort of thread is created to listen for requests from the user?

      Preferably by spawning a thread for each new connection. There's an example on MSDN on using sockets, with the server example here[^] and the client example here[^].

      I are Troll :)

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups