Closed
Bug 790028
Opened 14 years ago
Closed 10 years ago
Improve discoverability of registration server
Categories
(Testing Graveyard :: SUTAgent, defect)
Testing Graveyard
SUTAgent
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: mcote, Assigned: gbrown)
Details
At the moment, the registration server has to be configured in each phone's SUTAgent.ini file. If the registration server's address changes, or if we want to assign a phone to a different server, it is annoying and error prone to update it, especially if we need to update multiple phones.
bc suggested changing the SUTAgent to request a registration server on start up, e.g. by UDP broadcast. On start-up, it would send the request, and repeat it every, say, minute (maybe with exponential back off) until one is found (e.g. an acknowledgement is sent). We could even implement a heart beat with this that would cause the phone to resend its registration broadcast if, say, the server goes down. We can use the SUTAgent.ini pool setting in case there are multiple registration servers on the same subnet, so that the registration server would only respond to requests within its pool.
| Reporter | ||
Comment 1•14 years ago
|
||
This will be particularly useful when the device-pool code is split off from the rest of autophone.
| Reporter | ||
Comment 2•14 years ago
|
||
Hm see also bug 790041.
This is a great idea.
I'm all for it. And because the production code (as far as I know) still doesn't use the registration server ping we are free to customize this to our heart's content as long as the java and new agent's functionality match.
| Assignee | ||
Comment 4•10 years ago
|
||
The Android/Java version of sutagent is being removed in bug 1255527. (Negatus remains in use at this time.)
Assignee: nobody → gbrown
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Updated•8 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•