Bug 12346 - SC should generate UUID on first startup, then used by clients to uniquely identify the server
: SC should generate UUID on first startup, then used by clients to uniquely id...
Status: CLOSED FIXED
Product: SqueezePlay
Classification: Unclassified
Component: Networking
: unspecified
: PC Other
: P1 critical (vote)
: 7.4.0
Assigned To: Wadzinski Tom
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-06-11 09:56 UTC by Wadzinski Tom
Modified: 2009-10-05 14:34 UTC (History)
4 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wadzinski Tom 2009-06-11 09:56:46 UTC
This came out of a chat that Dean, Richard, and I just had. Especially now that server names can be changed, it would useful for clients to use something other than server name as a key to the server, since names will change and since also duplicate names can happen. 

The suggestion is that SC will generate a UUID during first startup and publish the UUID during serverstatus and slim discovery.
Comment 1 Jim McAtee 2009-07-09 17:55:48 UTC
Why not just use the IP address?  You can't have more than one server running on an IP, can you?
Comment 2 Brandon Black 2009-07-10 09:17:17 UTC
Because a lot of people's IP addresses change regularly, so with a dynamic IP and no associated SN account we really can't tell unique SC's apart.
Comment 3 Andy Grundman 2009-07-13 18:25:26 UTC
Added in 7.4 trunk change 27524.  It's stored in the pref 'server_uuid'.

Tom: do you want to do the work of adding it to serverstatus/discovery along with the SP changes needed?
Comment 4 Wadzinski Tom 2009-07-13 18:53:27 UTC
Andy, yes I'll pick it up from here
Comment 5 Richard Titmuss 2009-07-27 01:13:56 UTC
Reset priority before triage.
Comment 6 Wadzinski Tom 2009-08-05 04:53:54 UTC
 == Automatic comment from SVN commit #6916 to Repository: jive ==
https://svn.slimdevices.com/jive?view=revision&revision=6916

Fixed Bug:12346
Description:
- server uuid now used as server id (unless uuid not given, in which case name is used as id)


 == Modified 6 files total ==
7.4/private-branches/fab4/squeezeplay/src/squeezeplay/share/applets/HttpAuth/HttpAuthApplet.lua
7.4/private-branches/fab4/squeezeplay/src/squeezeplay/share/applets/HttpAuth/HttpAuthMeta.lua
7.4/private-branches/fab4/squeezeplay/src/squeezeplay/share/applets/Playback/PlaybackMeta.lua
7.4/private-branches/fab4/squeezeplay/src/squeezeplay/share/applets/SlimDiscovery/SlimDiscoveryApplet.lua
7.4/private-branches/fab4/squeezeplay/src/squeezeplay/share/applets/SlimDiscovery/SlimDiscoveryMeta.lua
7.4/private-branches/fab4/squeezeplay/src/squeezeplay/share/jive/slim/SlimServer.lua
Comment 7 James Richardson 2009-10-05 14:34:23 UTC
This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server!
    * SqueezeCenter: 28672
    * Squeezebox 2 and 3: 130
    * Transporter: 80
    * Receiver: 65
    * Boom: 50
    * Controller: 7790
    * Radio: 7790  

Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes

If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.