Abdullah Marafie (aam3)
Aaron Hamid (arh14)
Harmonize component interfaces. Set up central login/authentication/management server for both components and "management-clients". Write "management-clients" to communicate with management server and gather diagnostic information from other components.
// Data exchange
GetDataExchangeParams(?)
SetDataExchangeParams(?)
// Signaling
// Hooks will be callbacks to the management node when updated info is available
InitiateHook(?)
TerminateHook(?)
// Gateway
GetRoutingTable(?)
SetRoutingTable(?)
GetDataStatistics(?)
// Directory Services
InitiateHook(?)
TerminateHook(?)
Their normal interface will probably suffice.
We will have to see.
// Accounting
// dependent on pricing plan and options Accounting develops
GetAccountingParams(?)
SetAccountingParams(?)
// these may be in their standard interface once they design one
GetReport(?)
GetBill(?)
// average length of calls, type of each caller, number of calls, total amount charged, etc.
// Accounting will have to inform us of their options
GetAccountingStatistics(?)
// Authentication mechanism to be decided upon
Login(?)
Logout(?)
None, other than Login/Logout for major components, as of yet.
The above interfaces will have to be refined and supported by the respective components.
One hour meeting every Tuesday after class and general management responsibilities.
After the first meeting we should have a good idea of what flexibility compenents would like in login/logout procedures and what type of management data they can supply us. At this point it is difficult to specify a week-to-week schedule due to management’s high dependence on the other components’ schedules and interfaces.
1st wk: Decide upon login/logout/authentication procedures and code bare management server
2nd wk+: Refine component-management interfaces
Finally: Write front-end for management server (multiple remote "management-clients" which can access management info)
Advice on client-server authentication techniques.
The Simple Book