Fix: Switching from snowflake to fully random generated socket id about socketioxide

[biryukovmaxim]

Hey, I think that's not flexible enough, go and js implementations use String, but I can suggest using generic type Clone + Eq + Hash. If type is Copy it is easy to implement Clone for it.
It cab be implemented with Generator trait

pub trait Generator: Clone + Sync + Send + 'static + Debug {
    type Sid: Clone + Hash + Eq + Debug + Display + FromStr;
    fn generate_sid(&self) -> Self::Sid;
}

What do you think about it?

[biryukovmaxim]

I created a PR.
I haven't fixed docs test, it expects addition of type annotations.
From my point of view it can make project more complicated and less developer friendly.
Could you check it out? Now I'm not sure if it's really worth it

[Totodore]

As I said in your PR, it is maybe not the best moment to add so much complexity to the codebase due to the generic.
However you can still make a fixed implementation of a fully random, fixed size generated socket id. It is the part that's bother me the most because snowflakes are predictible.

[Totodore]

I like the idea of a Generator trait so it allows the user to specify a custom generator function.

But it would imply to propagate another generic all around the codebase.

Idk if it is worth it but why not try and see the result !

Are you considering working on it ?

[Totodore]

Resolved with #19