Storing the last event id to cookie

[flowersinthesand]

Inspired from https://groups.google.com/d/msg/jquery-socket/oudUrEfO0HM/gzwcyniNKKYJ and #38.

1. Create a new option which enables this function or not.
2. If the option is enabled and there is a stored id, replace lastEventId with the stored one when making url.
3. Every time the event is arrived, If the option is enabled and the event has an id, then save the event id into cookie.

Discussion

• Is it all right to write cookie?
• What if there are more than one sockets using this option?
• The number of cookie to be used.
• Cookie name and value format

[mkdgs]

for now i use localStorage instead cookie, but the goal and the odd is the same.
when more than one tab is open you can loose some events...

but for my use it's right, i can loose some events.

i think the better way is to have only one socket and sharing it... but the big question about that is how communicate across tabs.

[flowersinthesand]

Issue #21 covers sharing a socket across tabs, but I'm not sure it's feasible yet.

[mkdgs]

I think something is possible when i read this: http://www.codediesel.com/javascript/sharing-messages-and-data-across-windows-using-localstorage/