Lack of Websocket API Documentation

[bijenkins]

I've searched the source and I see the ability to use Websockets, and even noticed the example in the readme, which shows a very basic client example. Is there any documentation surrounding the Websocket API? There is a entire page on just the restful api, but searching the RTD; websocket is not even mentioned.

[acodercat]

me too

[soer7022]

+1

[soer7022]

I'm gonna try out an old project: WSCelery

[bobycloud]

+1

[akanoce]

Maybe the response comes a bit late, but for those still looking for the hidden flower's websockets here's something useful. Digging in the source code, i finally managed to found the wss endpoints:

• /api/task/events/task-succeeded/
• /api/task/events/task-sent/
• api/task/events/task-received/
• /api/task/events/task-started/
• /api/task/events/task-failed/
• /api/task/events/task-revoked/
• /api/task/events/task-retried/
• /api/task/events/task-custom/

[daveflr]

+1. why there is no documentation about WebSockets?

[jreed1701]

I think the /api/task/events API was removed recently.

[daveflr]

yup, webSockets API was completely deprecated in 1.1.0

[jreed1701]

Might as well close this issue then since no more websockets? I'll just lock to flower 1.0 to keep it. Thanks!

[dhs-rec]

Might as well close this issue then since no more websockets? I'll just lock to flower 1.0 to keep it. Thanks!

No, please don't close.

A long used functionality has been removed all of a sudden (even though the commit comment says "deprecate"). Deprecating something means: Mark it for removal in a LATER version while giving users a chance to migrate. This all didn't happen here, so the only viable solution is to add it back in.

Furthermore, the project has no changelog where users could have found information about the removal, and what to do/use instead.

[dhs-rec]

yup, webSockets API was completely deprecated in 1.1.0

Nope, it wasn't deprecated, it was silently REMOVED.