Difference between revisions of "Architecture Overview"

From reSIProcate
Jump to navigation Jump to search
m (replace image links to the old SVN repo with links to the Git repo)
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
The Stack's core transaction processing architecture uses a SIP message-based interface between the Transaction (and lower) layers and the Transaction User layers.
+
ReSIProcate's core transaction processing architecture uses a SIP message-based interface between the Transaction (and lower) layers and the Transaction User layers. The [[DUM Overview|Dialog Usage Manager]], which was created to simplify the creation of an user agent, is one example of a Transaction User.
DUM is one example of a Transaction User.
 
  
This diagram shows the reSIProcate Transaction and Transport Architecture.  Common colours indicate related, thread connected components.
+
The following diagram (PNG file [https://github.com/resiprocate/resiprocate/blob/master/resip/stack/doc/ResipArchitecture.png]) shows the ReSIProcate transaction and transport architecture.  Common colors indicate related, thread-connected components. This diagram is also available as PDF [https://github.com/resiprocate/resiprocate/blob/master/resip/stack/doc/ResipArchitecture.pdf] and graffle source  [https://github.com/resiprocate/resiprocate/blob/master/resip/stack/doc/ResipArchitecture.graffle]. The diagram was created with OmniGraffle Pro 3.0 [http://www.omnigroup.com/applications/omnigraffle/] and updated at the 2005Q2 ReSIProcate documentation session.
[[Image: http://scm.sipfoundry.org/rep/resiprocate/main/resip/stack/doc/ReSIP%20diagrams%20-%20Architecture.png ]]
 
<!-- [[Image:http://scm.sipfoundry.org/viewsvn/*checkout*/resiprocate/main/sip/resiprocate/doc/ResipArchitecture.jpg]] -->
 
 
 
The original diagram was made using OmniGraffle Pro 3.0 [http://www.omnigroup.com/applications/omnigraffle/] and is also available in the reSIProcate SCM repository as a PDF file [http://svn.resiprocate.org/viewsvn/resiprocate/main/resip/stack/doc/ResipArchitecture.pdf] , PNG file [http://svn.resiprocate.org/viewsvn/resiprocate/main/resip/stack/doc/ResipArchitecture.png] and the original graffle source  [http://svn.resiprocate.org/viewsvn/*checkout*/resiprocate/main/sip/stack/doc/ResipArchitecture.graffle].
 
 
 
NOTE: The diagram was updated at a recent (2005Q2) documentation session and includes the TU selector now. Unless someone needs a pretty version again, I'll defer to the controlled PNG as the architecture document.
 

Latest revision as of 10:28, 20 November 2016

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 (PNG file [1]) shows the ReSIProcate transaction and transport architecture. Common colors indicate related, thread-connected components. This diagram is also available as PDF [2] and graffle source [3]. The diagram was created with OmniGraffle Pro 3.0 [4] and updated at the 2005Q2 ReSIProcate documentation session.