Functionality to set cookie after connected

[evnchn]

In #4404, we were trying to set cookie after the initial HTTP connection and its window to set the cookie via HTTP Reponse headers has elapsed. Although this cannot be done with NiceGUI natively, there exist 2 workarounds:

1. Set cookie via ui.run_javaascript()
2. Set cookie via navigating to another page and then back, thus set the cookie using another set of HTTP Response headers
   a. Could be doable with a background iframe / background Fetch request, but we can look into that later.

Please upvote if you think this functionality is worth it, and be sure to explain why you are using the cookies instead of app.storage.user, for example. Thanks!

[jinhong-china]

The app. storage.user method takes up server memory and loses sessions after closing the browser, so a persistent way to store tokens is needed. The app.storage.browser method also doesn't work. I tried asynchronous httpx requests to obtain tokens and store them in app. storage. browser, but it still couldn't be implemented. It seems to be an asynchronous mechanism issue At present, for me, the only option to implement login requests and store cookies is run.javascript

[rodja]

The app. storage.user method takes up server memory and loses sessions after closing the browser, so a persistent way to store tokens is needed.

Can you elaborate? What do you mean by "losing the session after closing the browser"? app.storage.user persistently stores the data on the server and identifies the user with a session cookie -- which reidentifies the data in the next connection.

The app.storage.browser method also doesn't work.

Yes, because it is an http only cookie. If you really want to store things in the browser, ui.run_javascript is by far the simplest way to do it right now.

[jinhong-china]

该app. storage.user方法会占用服务器内存，并在关闭浏览器后丢失会话，因此需要一种持久化的方式来存储令牌。

你能详细说明一下吗？你说的“关闭浏览器后会话丢失”是什么意思？它app.storage.user会将数据持久存储在服务器上，并通过会话 cookie 来识别用户——这样在下次连接时就可以重新识别数据。

这种app.storage.browser方法也行不通。

是的，因为它是一个仅限 HTTP 的 cookie。如果您确实想在浏览器中存储数据，ui.run_javascript这是目前最简单的方法。

I have not used the method app.storage.user so far. The current introduction about it is that the state is stored on the server and only maintains the current session There is no explanation of the subsequent connection situation, so the understanding is not detailed However, this storage method on the server is not what I need What I need is to store it in the user's browser And app. storage. browser cannot meet my expectations. nice gui cannot store browser cookies natively, so currently only run_JavaScript is available. However, I think this is not enough. nice gui needs a method that can solve asynchronous storage of browsers or direct storage of cookies

[rodja]

What I need is to store it in the user's browser

That is really interesting. Can you explain to us why you need this? What is the reason you explicitly need to store it in the browser? We are open to new features but we need to understand the requirements and scenarios where it is used to find the right API and make devs happy 😀

[jinhong-china]

我需要将它存储在用户的浏览器中。

这真的很有意思。您能解释一下为什么需要这个功能吗？为什么一定要把它存储在浏览器中？我们乐于接受新功能，但我们需要了解具体的需求和使用场景，才能找到合适的 API，让开发者满意 😀

To reduce server memory usage and improve concurrent performance

[rodja]

To reduce server memory usage

Really? How much data do you want to save? How many users do you expect?

and improve concurrent performance

Have you profiled the performance and found it bad? As I understand it, each file is written async in the background and does not lock other files. I would bet quite a bit that storing on the server is faster than transmitting (large) amounts of data from browser cookies back and froth.