Difference between revisions of "Midware TAppServer"

From Overbyte
Jump to navigation Jump to search
(Corrected a typo error)
Line 13: Line 13:
 
|-
 
|-
 
| valign="top" | [[Midware_TAppServer.ClientCount | ClientCount]] |||| Gives the actual number of connected clients.
 
| valign="top" | [[Midware_TAppServer.ClientCount | ClientCount]] |||| Gives the actual number of connected clients.
 +
|-
 +
| valign="top" | [[Midware_TAppServer.ClientCountLabel | ClientCountLabel]] |||| If assigned, this property will be used by TAppServer component to display the number of client connected.
 +
|-
 +
| valign="top" | [[Midware_TAppServer.ClientTimeout | ClientTimeout]] |||| ClientTimeout gives the time in seconds before the server disconnect a client without activity.
 +
|-
 +
| valign="top" | [[Midware_TAppServer.ClientWSocket | ClientWSocket]] |||| ClientWSocket is a run-time read-only indexed property whose value is the reference to each connected client TClientWSocket component.
 +
|-
 +
| valign="top" | [[Midware_TAppServer.ConnectCount | ConnectCount]] |||| ConnectCount gives the total number of connection received since server startup.
 +
|-
 +
| valign="top" | [[Midware_TAppServer.DisplayMemo | DisplayMemo]] |||| If assigned, this property will be used by TAppServer component to display messages during work.
 +
|-
 +
| valign="top" | [[Midware_TAppServer.Handle | Handle]] |||| The Handle property is the windows handle for the hidden window the component uses for internal messages
 +
|-
 +
| valign="top" | [[Midware_TAppServer.Handle | Handle]] |||| The Handle property is the windows handle for the hidden window the component uses for internal messages.
 +
|-
 +
| valign="top" | [[Midware_TAppServer.Port | Port]] |||| The port property gives the port number or service name used by the server to listen for client connection.
 +
|-
 +
| valign="top" | [[Midware_TAppServer.xyz | xyz]] |||| abc
 +
|-
 +
| valign="top" | [[Midware_TAppServer.xyz | xyz]] |||| abc
 +
|-
 +
| valign="top" | [[Midware_TAppServer.xyz | xyz]] |||| abc
 +
|-
 +
| valign="top" | [[Midware_TAppServer.xyz | xyz]] |||| abc
 +
|-
 +
| valign="top" | [[Midware_TAppServer.xyz | xyz]] |||| abc
 +
|-
 +
| valign="top" | [[Midware_TAppServer.xyz | xyz]] |||| abc
 +
|-
 +
| valign="top" | [[Midware_TAppServer.xyz | xyz]] |||| abc
 +
|-
 +
| valign="top" | [[Midware_TAppServer.xyz | xyz]] |||| abc
 
|}
 
|}
  

Revision as of 10:02, 2 May 2011

Main page -> Midware component reference -> TAppserver

Overview

unit ApServer.pas

TAppServer is the communication kernel for all MidWare application servers. This component handle all the communication work for the application server, keeping track of user connections and sessions. A complete application server is made of a TAppserver component, a TRequestBroker (Object Request Broker) component and a set of TServerObject descendent components.

Properties

Banner The banner property is the text that is sent to the client when the connection has been established. Default value is 'Welcome to MidWare server'.
ClientCount Gives the actual number of connected clients.
ClientCountLabel If assigned, this property will be used by TAppServer component to display the number of client connected.
ClientTimeout ClientTimeout gives the time in seconds before the server disconnect a client without activity.
ClientWSocket ClientWSocket is a run-time read-only indexed property whose value is the reference to each connected client TClientWSocket component.
ConnectCount ConnectCount gives the total number of connection received since server startup.
DisplayMemo If assigned, this property will be used by TAppServer component to display messages during work.
Handle The Handle property is the windows handle for the hidden window the component uses for internal messages
Handle The Handle property is the windows handle for the hidden window the component uses for internal messages.
Port The port property gives the port number or service name used by the server to listen for client connection.
xyz abc
xyz abc
xyz abc
xyz abc
xyz abc
xyz abc
xyz abc
xyz abc

Methods

DisconnectAll Disconnect every connected client. Do not confuse with the Stop method.
Start The start procedure will start the server. The server will accept new client connections. See also Stop.

Events

OnAfterProcessRequest The OnAfterProcessRequest is called when a request has been processed by a TServerObject.
OnAfterSendReply The OnAfterSendReply event is called once the reply header and body has ben written to the internal buffer for sending in the background.

How to


Midware Components Reference