Thnx for bringin this up. I have been cursing these session problems since I started to use surf. I just don't know C well enought to catch the problem and I have looked it also from wrong place. I was sure it was SOAP-problem.
Does this mean that I can solve this problem by making some hack that keeps track of my cookies and makes sure that my cookies.txt will be in it's real state, not in some surf-process state? I'm using multiple surf processes all the time, 'cause I want to keep some sites (like my webmail) open. And it's very annoying that it throws me out every now and then. My best, Erno Kuvaja On Thu, 11 Mar 2010 14:52:15 +0300, anonymous <aim0s...@lavabit.com> wrote: > Use stable version. Now most of cookies-related code is removed and it > will be rewritten for multi-process design. The problem with existing > cookies code is that it stores cookies when you exit and reloads when you > start new surf process. So if you run 2 surf processes, login in first, > close it and then close second, the second will store empty cookies.txt > again and rewrite cookies stored by first process. It is common situation, > you can see something like it when bash stores its history.
