| | 1 | = Including opaque data in scheduler request messages = |
| | 2 | |
| | 3 | If the file '''client_opaque.txt''' exists in the client data directory, |
| | 4 | it will be included in scheduler request messages as follows: |
| | 5 | {{{ |
| | 6 | <client_opaque> |
| | 7 | <!{CDATA[ |
| | 8 | (contents of client_opaque.txt) |
| | 9 | ]]> |
| | 10 | </client_opaque> |
| | 11 | }}} |
| | 12 | and will be read into the string '''SCHEDULER_REQUEST::client_opaque''' on the server, |
| | 13 | where it can be accessed by customizable scheduler functions. |
| | 14 | |
| | 15 | This mechanism lets you, for example, designate particular hosts as |
| | 16 | being trusted, having some software resource installed, and so on. |
| | 17 | |
| | 18 | This is implemented in version [24586] of the server code. |
| | 19 | It will work with client versions 6.13.11+. |
