Difference between revisions of "Architecture Overview"

From reSIProcate
Jump to navigation Jump to search
m
Line 3: Line 3:
  
 
This diagram shows the reSIProcate Transaction and Transport Architecture.  Common colours indicate related, thread connected components.
 
This diagram shows the reSIProcate Transaction and Transport Architecture.  Common colours indicate related, thread connected components.
 +
[[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]] -->
  
[[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://scm.sipfoundry.org/viewsvn/*checkout*/resiprocate/main/sip/stack/doc/ResipArchitecture.pdf] , PNG file [http://scm.sipfoundry.org/viewsvn/*checkout*/resiprocate/main/sip/stack/doc/ResipArchitecture.png] and the original graffle source  [http://scm.sipfoundry.org/viewsvn/*checkout*/resiprocate/main/sip/stack/doc/ResipArchitecture.graffle].
  
This 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://scm.sipfoundry.org/viewsvn/*checkout*/resiprocate/main/sip/resiprocate/doc/ResipArchitecture.pdf] , PNG file [http://scm.sipfoundry.org/viewsvn/*checkout*/resiprocate/main/sip/resiprocate/doc/ResipArchitecture.png] and the original graffle source  [http://scm.sipfoundry.org/viewsvn/*checkout*/resiprocate/main/sip/resiprocate/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.

Revision as of 22:37, 22 August 2005

The Stack's core transaction processing architecture uses a SIP message-based interface between the Transaction (and lower) layers and the Transaction User layers. DUM is one example of a Transaction User.

This diagram shows the reSIProcate Transaction and Transport Architecture. Common colours indicate related, thread connected components. File:Http://scm.sipfoundry.org/rep/resiprocate/main/resip/stack/doc/ReSIP diagrams - Architecture.png

The original diagram was made using OmniGraffle Pro 3.0 [1] and is also available in the reSIProcate SCM repository as a PDF file [2] , PNG file [3] and the original graffle source [4].

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.