forkwhilefork
commented
2 years ago There are a few aspects to this.
One part is that the server’s data needs to persist past a server restart. That would be easy to achieve by serializing important operational data (maybe just the peer objects?), writing it to disk every ~minute (if there’s been a change), and reading that file to initialize when the server starts up.
The other part involves matching up users with their sessions, which probably requires making a user/login system. That’s a lot more work. :/
It would be useful to allow BGP sessions to persist past the lifetime of a browser session. Then a user could e.g. work for a while and come back to something later without having to re-set-up all of their session data.
This would also allow multiple sessions at a time for a given user, so you'd need some "list of all sessions" page.
This issue is mostly an enabler for #6.