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 3, 2010, 12:26:31 AM (14 years ago)
- Author:
-
salinasv
- Comment:
-
Add stack figure
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v3
|
v4
|
|
2 | 2 | There will be a self contained stack that makes transparent to every other module about the details of SLP and SLP messages. The proposed architecture exposes a single SLP API on top of the stack and pass it to the lower layers as needed: SLP API → !SlpCall → !SlpLink → Network. Where !SlpLink is an abstraction of the possible transaction methods, each defined in the !DirectConn and SBConn modules. |
3 | 3 | |
| 4 | {{{ |
| 5 | +------------+ |
| 6 | | SLP API | |
| 7 | +------------+ |
| 8 | | |
| 9 | +------------+ |
| 10 | | SlpCall | |
| 11 | +------------+ |
| 12 | | |
| 13 | +------------+ |
| 14 | | SlpLink | |
| 15 | +------------+ |
| 16 | / \ |
| 17 | +------------+ +------------+ |
| 18 | | SBConn | | DirectConn | |
| 19 | +------------+ +------------+ |
| 20 | \ / |
| 21 | +------------+ |
| 22 | | Network | |
| 23 | +------------+ |
| 24 | Figure 1. SLP Stack |
| 25 | }}} |
4 | 26 | === SLP API (WIP) === |
5 | 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 |
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!