canmove, Confirmed users
1,173
edits
Services/NodeAssignment: Difference between revisions
→Design
(→Design) |
|||
| Line 57: | Line 57: | ||
==Design== | ==Design== | ||
The user's nodes will be stored in the authentication LDAP, in an array under the primaryNode attribute. The storage format will be | The user's nodes will be stored in the authentication LDAP, in an array under the primaryNode attribute. The storage format will be node<internal information. Internal information consists of arbitrary data, as defined by the product. | ||
In a situation where the user already has an assignment corresponding to the product, authenticating the user will be sufficient, as the data from that will be sufficient to fulfill the response. | In a situation where the user already has an assignment corresponding to the product, authenticating the user will be sufficient, as the data from that will be sufficient to fulfill the response. | ||
If there is no record for the product in the primaryNode field, the application will request an assignment from the assignment table. This is a mysql table that will evaluate the available nodes for a product, and produce the one with the best current availability, returning the data to be written into LDAP. | If there is no record for the product in the primaryNode field, the application will request an assignment from the assignment table. This is a mysql table that will evaluate the available nodes for a product, and produce the one with the best current availability, returning the data to be written into LDAP. | ||
==DB Fields== | ==DB Fields== | ||