Another program takes each of the resource files and,
depending upon the type of resource,
passes it to another process or machine that knows how
to allocate the requested resource.
For instance, the mfcf.math computing file goes
to the machine mfcf.math itself, where a program compares
that file with the current state of the machine.
If the resource file lists an account that doesn't exist
on the machine, the mechanism immediately creates such an account.
Similarly if an account exists on the machine
but doesn't appear in the file,
that account no longer has any sponsors
and so an account deletion mechanism takes over the account.
For sponsored accounts that do exist,
it adjusts disk quotas and group memberships as necessary,
including handling cases of multiple sponsorship.
For Nexus accounts, the resource file goes to student.math,
where a program compares it with a dump of the
existing Nexus accounts.
Any differences result in a MS-DOS batch file
containing add and delete commands that
the perseus.math PC then processes.
For Active Directory accounts, the resource file goes to mfcf.math
where a program queries our AD server
and compares the results with these requests.
LDAP commands immediately correct any differences
(e.g. new accounts, expired accounts, group membership).
Note that in each case, quite different mechanisms
handle the compiled resource request files,
sometimes by the accounts-master machine itself,
sometimes by a second machine, and sometimes by
the target machine via an intermediate machine.
The exact mechanisms depend upon the type of resource
but not upon the sponsorship data itself,
allowing implementation changes and reconfiguration
without affecting or requiring changes to anything else.