Extend socket's life cycle over multiple pages about cettia-javascript-client HOT 2 CLOSED

The above scope we discussed is called browsing context according to W3C's HTML5 spec and it seems that window.name is the only storage sharing its life cycle with browsing context. Since it is just the name of the window, our use case may be a misuse and not reliable but I couldn't find a better alternative or a unobtrusive solution.

For this feature, we need a new option, name?: string. name is an identifier of a socket within document and used to identify a specific socket in each document within browsing context. A user should define it explicitly as it can't have default value.

// A socket whose name is 'main' after page navigation will continue this socket's life cycle
cettia.open("/cettia", {name: "main"});

Actually, uri might be suitable as the default value of name option but if two sockets sharing the same uri exist in the same page or uri is generated programmatically e.g. cettia.open("/cettia?time=" + Date.now()), it won't work.

Now we need how to use window.name to get/set data indicating that which name corresponds to which socket.

from cettia-javascript-client.

Because a way depending on window.name itself is obstructive unlike cookie or session storage, there is no way to avoid conflicting with existing libraries using window.name. That's why it doesn't matter even if we monopolizes window.name. Of course user should be aware of that.

As for how to use window.name, window.name will be a JSON representation of an object whose key is name option and value is socket id. That's all.

from cettia-javascript-client.