Trac is being migrated to new services! Issues can be found in our new
YouTrack instance and WIKI pages can be found on our
website.
- Timestamp:
-
Jun 14, 2010, 11:05:52 PM (14 years ago)
- Author:
-
salinasv
- Comment:
-
Document SlpMsgPart?
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v8
|
v9
|
|
6 | 6 | | SLP API | |
7 | 7 | +------------+ |
8 | | | |
| 8 | | SlpMessage |
9 | 9 | +------------+ |
10 | 10 | | SlpCall | |
… |
… |
|
14 | 14 | | SlpLink | |
15 | 15 | +------------+ |
16 | | / \ |
| 16 | / \ SlpMessagePart |
17 | 17 | +------------+ +------------+ |
18 | 18 | | SBConn | | DirectConn | |
19 | 19 | +------------+ +------------+ |
20 | | | | |
| 20 | MsnMsg | | |
21 | 21 | +------------+ +------------+ |
22 | 22 | |Switchboard | | Network | |
… |
… |
|
25 | 25 | }}} |
26 | 26 | === SLP API (WIP) === |
27 | | This API must abstract everything others modules will need from SLP transactions. This will be the one that creates the !SlpCall for any new transaction as needed |
| 27 | This API must abstract everything others modules will need from SLP transactions. This will be the one that creates the !SlpCall for any new transaction as needed. |
| 28 | |
| 29 | Here is where the !SlpMessage is created and passed down to lower modules. |
28 | 30 | |
29 | 31 | === !SlpCall === |
… |
… |
|
33 | 35 | Abstract a Connection. Try !DirectConn and fallback to SBConn if the former fails. This module is also responsible to get the data that must be sent from files or write down the received data. |
34 | 36 | |
| 37 | If the data that will be sent is big, here it is split in a serie of !SlpMsgPart to be sent down to a Conn. |
| 38 | |
35 | 39 | === Conn === |
36 | 40 | This modules must expose a common interface so they can be easily attached to !SlpCall and Network interfaces. |
| 41 | |
| 42 | ==== SBConn ==== |
| 43 | Each SlpMsgPart must be packaged in a MsnMessage and then be sent through the !Switchboard. |
37 | 44 | |
38 | 45 | == Packagement == |
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!