Bug 13844 - SP should not connect slimproto to SN or issue menu requests until registered
: SP should not connect slimproto to SN or issue menu requests until registered
Status: CLOSED FIXED
Product: SqueezePlay
Classification: Unclassified
Component: Networking
: unspecified
: PC Other
: P1 normal (vote)
: 7.4.0
Assigned To: Wadzinski Tom
:
Depends on:
Blocks: 13799 13836
  Show dependency treegraph
 
Reported: 2009-09-03 15:43 UTC by Andy Grundman
Modified: 2009-10-05 14:29 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andy Grundman 2009-09-03 15:43:47 UTC
SP should check the comet session ID during comet handshake/connect.  If the session starts with 1X, it is unregistered.  In this state, SP should not connect to SN via slimproto or issue any CLI commands that would talk to slimservice.  serverstatus and registration-related commands are OK.

After registration, SN forces a comet reconnect and will then return a session that contains a valid user id (<userid>X...) and then slimproto/CLI commands will work.  Also any CLI commands sent should wait until slimproto has connected.
Comment 1 SVN Bot 2009-09-04 08:33:46 UTC
 == Auto-comment from SVN commit #7414 to the jive repo by tom ==
 == https://svn.slimdevices.com/jive?view=revision&revision=7414 ==

Fixed Bug:13844 +2
Description:
- don't fetch menus if SP not registered with SN
Comment 2 James Richardson 2009-10-05 14:29:06 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.