Getting timed out message from socket on subscribe or presence

[centrifugal]

Getting timed out message from socket on subscribe or presence

[FZambia]

@foobargeez thanks for report, just for information, what Centrifugo engine do you use - Memory or Redis?

[foobargeez]

Memory (at the moment).

[FZambia]

The code in examples written in synchronous style. In synchronous code it's hard to restart application state from scratch after subscription errors like this. Because program flow goes forward and client can't step back. Maybe event-driven approach is better for this? Just made a gist to demonstrate:

https://gist.github.com/FZambia/9d9f3ed31897fd6736c9cd6a7ff7ad0d

This allows to restart subscription after error occurred.

[FZambia]

Also maybe sth like this?

	c := centrifuge.New(wsURL, creds, events, centrifuge.DefaultConfig())

	var sub *centrifuge.Sub

	for {
		err := c.Connect()
		if err != nil {
			log.Fatalln(err)
		}

		subEvents := centrifuge.NewSubEventHandler()
		subHandler := &subEventHandler{}
		subEvents.OnMessage(subHandler)
		subEvents.OnSubscribeSuccess(subHandler)
		subEvents.OnUnsubscribe(subHandler)

		sub, err = c.Subscribe("public:chat", subEvents)
		if err != nil {
			c.Disconnect()
			continue
		}
		break
	}

        // Do sth with subscription...

[FZambia]

Merged branch with SubscribeAsync method to subscribe asynchronously, example here