Suggestions for next version

[ghost]

Here is a short list of new freatures that can be really helpfull for client and server

Server :

Add the possibility to make the cors origins as an array, to allow multiples origins :

const server = geckos({
	cors: { origin: ["https://origin1.com", "https://origin2.com"]}
});

Server and client :

We should be abe to detect any upcoming message without taking care of the name, like that :

channel.onAny(function() {
	//Do something
});

Remove messages listeners :

channel.removeListeners("name"); //Remove all listeners for "name" message

const listener = channel.on("name", function() {
	//...
})

channel.removeListener(listener); //Remove the specific listener

And to detect specific message name only one time :

channel.once("name", function() {
	//...
})

Client :

Would be really helpfull for the games with multiples servers to switch the server url and port by saving the message listeners :

channel.switchServer(/*newURL*/);
channel.switchPort(/*newPort*/);

It's not about geckos.io, but it's related, idk if it's possible, but would be cool to allow to use an array instead of object in https://github.com/geckosio/typed-array-buffer-schema

Would work like that :

const packShema = BufferSchema.schema("test", [{
    id: uint8,
    x: int16,
    y: int16,
}]);

//Or

const testShema = BufferSchema.schema("test", {
    id: uint8,
    x: int16,
    y: int16,
});

const packShema = BufferSchema.schema("pack", [testShema]);

const packModel = new Model(packShema);

const myPack = [{
	id: 1,
	x: 500,
	y: 750,
},
{
	id: 2,
	x: 200,
	y: 750,
},
{
	id: 3,
	x: 6,
	y: 1688,
}]

const buffer = packModel.toBuffer(myPack);

Then if the buffer contain only one type of entity, we don't have t create an object for only one array on it