Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Server maintenance mode #146

Closed
ar2rsawseen opened this issue May 22, 2015 · 6 comments
Closed

Server maintenance mode #146

ar2rsawseen opened this issue May 22, 2015 · 6 comments

Comments

@ar2rsawseen
Copy link
Member

Provide an option to enable server maintenance mode which either responds 503 for SDK requests to make them queue requests and sync back later

or make server side queue in another db, that can be relaunched later on

@gorkem-cetin
Copy link
Contributor

Out of curiosity, would there by any SDK changes for this to happen?

@ar2rsawseen
Copy link
Member Author

No, server response with service unavailable, which is not success code, so no changes there if SDK properly listens to response codes, which I think all official ones do :)

@gorkem-cetin
Copy link
Contributor

Just FYI: there's a check needed for Unity & cocos2d-x at least, will also ping for Appcelerator.

@osoner
Copy link
Member

osoner commented Jul 24, 2015

The queue implementation should take care of this in all SDKs. Device having no internet connection and maintenance mode should basically be the same thing for the SDKs, no HTTP 200 response.

@ar2rsawseen
Copy link
Member Author

but not everyone will have queue db, so SDK should look for success HTTP response code and possible for JSON response with result property equal to Success.

I think we could write SDK implementation guide

@gorkem-cetin
Copy link
Contributor

An implementation guide would be great. All SDKs have started to become different from each other in terms of features and methods of work. I'm trying to get them aligned talking to other SDK devs, but a generic doc would be great.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants