Difference between revisions of "APEL/Server"
< APEL
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
'''This page is under construction and is not yet complete.''' | '''This page is under construction and is not yet complete.''' | ||
== APEL Server Design == | == APEL Server Design == | ||
Line 10: | Line 7: | ||
* Record publisher | * Record publisher | ||
* Authentication | * Authentication | ||
== APEL STOMP Testing == | |||
[[APEL/APELSSMExternalTesting|APEL SSM Testing]]: If you are interested in testing the new STOMP interface or want to develop your own client. | |||
== APEL Message Format == | == APEL Message Format == |
Revision as of 11:44, 18 January 2012
This page is under construction and is not yet complete.
APEL Server Design
The new APEL server is written in Python. Its design is described in APEL Server Design. It has four components:
- SSM
- Record loader
- Record publisher
- Authentication
APEL STOMP Testing
APEL SSM Testing: If you are interested in testing the new STOMP interface or want to develop your own client.
APEL Message Format
SSM
The SSM is the messaging system used by APEL to transmit messages. It is written in Python and uses the STOMP protocol.
Record loader
This has the fairly simple job of taking the received messages and putting them in the database.
Record publisher
This takes the information from a database and produces messages.
Authentication
This verifies that the senders of the messages via the SSM are known to APEL.