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

Implement new and cache event #3

Closed
flowersinthesand opened this Issue Jun 2, 2015 · 0 comments

Comments

Projects
None yet
1 participant
@flowersinthesand
Member

flowersinthesand commented Jun 2, 2015

Since Alpha1, socket's life cycle's beginning and end have corresponded to open and close event respectively. Now that socket's life cycle is extended, we need a special event to define the beginning of new life cycle and the end of old life cycle and it is the new event. In other words, the period between new events is the complete life cycle of socket. It is called when the server issues a new id shortly before open event and takes no arguments.

Along with this concept, it is no longer an error but an event to send an event where there is no connection. The cache event is the very event to deal with such situation. It is called when an event is sent when there is no connection and takes an array of event name, event data, resolved callback and rejected callback.

With these events, a user can accumulate events which couldn't be sent during disconnection to a queue on cache event and send them again on next open event and manage resources including that cache sharing the same life cycle with socket on new event. For the overall context of this feature, see cettia/cettia-protocol#1.

@flowersinthesand flowersinthesand added this to the 1.0.0-Alpha2 milestone Jun 2, 2015

flowersinthesand added a commit that referenced this issue Jun 6, 2015

flowersinthesand added a commit that referenced this issue Jun 6, 2015

@flowersinthesand flowersinthesand self-assigned this Feb 11, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment