-
Notifications
You must be signed in to change notification settings - Fork 302
Architecture Overview
Scott Godin edited this page Jan 29, 2021
·
1 revision
ReSIProcate's core transaction processing architecture uses a SIP message-based interface between the Transaction (and lower) layers and the Transaction User layers. The Dialog Usage Manager, which was created to simplify the creation of an user agent, is one example of a Transaction User.
The following diagram:
shows the ReSIProcate transaction and transport architecture. Common colors indicate related, thread-connected components. The diagram was created with OmniGraffle Pro 3.0 http://www.omnigroup.com/applications/omnigraffle/ and updated at the 2005Q2 ReSIProcate documentation session.
- Navigation
- Developers
- Packages
- Community