/ ss cc [~danielpassos] So this has some interesting consequences for the UPS life cycle. Right now we assume that when the success callback is called we are registered with all of the categories, have a token, etc. Now happens inside of a service that we extend. However, what does this mean for the register method?
For starters, all of the methods we call are non blocking so we can kill the Callback method (YAY!), but this means that failures to connect to UPS are now handled by a service and not communicated to the client (boo!). There are several solutions to this, but none of them are a clear cut winner.
1) We continue to use the callback, but don't call it until the registration state with UPS is determined.
2) We register a handler that is called with the connection state passed to it (similar to how Google's client SDKs work)
3) UPS state is totally handled by our libraries. Developers will tell us what state they want us to be in and the library will fight the good fight keeping the device in that state.
wdyt?
|
