Don't require a connection id to use mg_wakeup

[jameshilliard]

Makes broadcasts cleaner I think.

See: #2786

[scaprile]

Sorry, this breaks the very essence of having this function in the first place.
https://mongoose.ws/documentation/tutorials/core/multi-threaded/

[jameshilliard]

Sorry, this breaks the very essence of having this function in the first place.

Maybe I'm misunderstanding but I thought the purpose of this function is to pass data to the mongoose thread from a separate thread. I'm not sure how this would break anything.

[cpq]

@jameshilliard you can send wakeup to the listening connection, if you don't have any specific connection to wake up.

[jameshilliard]

you can send wakeup to the listening connection, if you don't have any specific connection to wake up.

I mean, you technically can but it seems to be a lot of excess complexity vs something along these lines, sending to the listing connection for a broadcast like this just seems to be weird to me. You can also see in the multithreading example how this is also a pretty significant reduction in lines of code and cleaner api for broadcast type operations.