Re: [dev] surf+tabbed and session management

From: hiro <23hiro_AT_gmail.com>
Date: Fri, 14 Apr 2017 16:10:51 +0200

just for inspiration:

check out the format in .opera-12/sessions/autosave.win
plaintext .ini format, keeps history per tab, including title, url,
position, etc.
it's easy to parse, extract valuable information and stash away bookmarks.
file is being written regularly (on changes, but probably with a rate-limit).

personally i think tabs are stupid. there should be one url and title
per process.
problem is: you still need one history per tab/window/process.
if you want to keep it compatible with having just one single session
file in opera format all those different processes have to synchronize
via one process that then writes into the session file before
requesting a new site or going back/forward in history.

On 4/14/17, Enrico Weigelt, metux IT consult <enrico.weigelt_AT_gr13.net> wrote:
> Hi folks,
>
>
> I'm currently looking for a clean way to implement an session management
> similar to what we already on chrome + onetab. Basicly two main goals:
>
> a) when restarted it should open up all tabs (and windows) just like
> they were before the last termination.
> b) allow stashing away tabs, so they can be picked up again later
>
> Maybe that all could be combined w/ bookmarks: having some bookmark
> storage (or -server), and split up these things via separate
> directories. The sessions would just be subdirectories within the
> big bookmark tree, and the session restart logic would just start
> up individual surf and tabbed instances based on that data.
> On the other side, surf could be extended to update it's status
> within its given session ID.
>
> Similar things could be done w/ history. Maybe we could write a small
> daemon (eg via 9P) which does the bookkeeping, and surf just talks
> to the socket/path given via command line.
>
>
> --mtx
>
>
Received on Fri Apr 14 2017 - 16:10:51 CEST