Difference between revisions of "Architecture Overview"

From reSIProcate
Jump to navigation Jump to search
m
Line 6: Line 6:
 
[[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]]
  
This file is generated by OmniGraffle Pro 3.0 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] and the original graffle source  [http://scm.sipfoundry.org/viewsvn/*checkout*/resiprocate/main/sip/resiprocate/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].

Revision as of 20:38, 3 February 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/viewsvn/*checkout*/resiprocate/main/sip/resiprocate/doc/ResipArchitecture.jpg

This 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].