| | 629 | |
| | 630 | ==== w/o 4/7-4/13 ==== #w29 |
| | 631 | Process chain tracking, priorities, and contexts. |
| | 632 | |
| | 633 | When we consider that several services may actually need ordering for the stack to operate property, we start thinking of execution priorities and process chain handling amongst the server uplinks. To get this working, we add two more contexts - a server priority (sort of like preorder/postorder processing of modules) and server process directives, similar to Floodlight Commands. Process directives are ultimately translated to Commands, so they are more or less the same. Directives, however, are tied to message processing behavior beyond that of a Command, since a message's standard Floodlight context does not survive past escalation, but directives do. A directive may be recovered after a message's return, or be re-interpreted as a return command to be applied to the return path. |
| | 634 | |
| | 635 | ==== w/o 4/14-4/20 ==== #w30 |
| | 636 | Testing with a preliminary example: |
| | 637 | |
| | 638 | * tier 1: proxy |
| | 639 | * tier 2: forwarding, authentication |
| | 640 | |
| | 641 | Processing conflicts will arise if forwarding functions are executed before authentication. This type of conflict cannot be resolved by simply juggling around tiers, since tier 1 will still receive both forwarding table rules from the respective services. So we assign a higher priority to authentication so that it is checked first. |
| | 642 | |
