change nomenclature of api feature "chat" and associated methods

[mpareja-godaddy]

Feeling: Changing the nomenclature of api chatroom to more generic pub/sub would encourage more creative use of the api feature.

Thoughts ?

[evantahler]

Do you have any suggestions for a new name or new API?

Perhaps something like:

pubsub.broadcast(namespace: string, message: any);
pubsub.on((namespage: string, message: any) => doStuff()) 

I'm guessing the say and onSayRecieve middlewares are what would need the most change.

[mpareja-godaddy]

Agreed

[mpareja-godaddy]

Although superficial, the inference to other standard pub/sub frameworks plays better in fundamental understanding and should promote adoption and usage.

[evantahler]

When we do this rename, it may be time to add a regularly-requested feature to the chat system - persistence. We can store the last N messages in redis for easy retrieval in TTL'd buckets (by minute?) so they'll expire after a short window.