Difference between revisions of "Midware TServerObject"
Jump to navigation
Jump to search
| Line 8: | Line 8: | ||
Writing an application server is mostly writing TServerObject. Application server performance entirely depends on TServerObject performance. | Writing an application server is mostly writing TServerObject. Application server performance entirely depends on TServerObject performance. | ||
| + | |||
| + | == Properties == | ||
| + | {| | ||
| + | | width="140" valign="top" | [[Midware_TServerObject.FFunctionCode | FFunctionCode]] |||| The FunctionCode is used by the ORB to know how to dispatch client requests to the various server objects he has in his table. | ||
| + | |- | ||
| + | | valign="top" | [[Midware_TServerObject.FLniFileName | FLniFileName]] |||| Initialized by ORB with INI filename. Used for persistant data. | ||
| + | |} | ||
Revision as of 08:21, 9 May 2011
Main page -> Midware component reference -> TServerObject
Overview
| unit |
TServerObject is the ancestor (abstract class) for all objects responsible for doing the application server work. The ORB create instances of server object, pass client request to them and call their Execute method. When the server object work is done, it must call the Finish method to send the response back to the client. This can be done either from the Execute method or form any other point later in time.
Writing an application server is mostly writing TServerObject. Application server performance entirely depends on TServerObject performance.
Properties
| FFunctionCode | The FunctionCode is used by the ORB to know how to dispatch client requests to the various server objects he has in his table. | |
| FLniFileName | Initialized by ORB with INI filename. Used for persistant data. |
