Session Services
Session service components define task-specific behavior for components in the presentation tier. For example, a user enters information to update a customer using a dynamic server page, but a session service is called to actually perform the data update.
Session services can be used to:
- Manage referential integrity and transactions
- Implement behavior and operations involving one or more entities
- Expose disconnected XML record sets to client components
- Maintain the server side of the conversational state
Session service components are usually stateless, so Uniface provides special triggers for setting and getting state information. Component operations on session services exchange data as disconnected XML record sets, which are described by Document Type Definitions (DTDs). These DTDs are automatically generated if the session service components are generated by Uniface rather than created manually.
Technically, there is almost no difference between a session service and a regular service. To create a session service, create a Service and change the Component Type to 4 (Session Service) and set the value of the <$cmpStatemanagedBy> (State Managed By) property.
