From mint-bounce@lists.fishpool.fi Wed Sep 29 18:12:10 2010 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:x-priority:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=Jnrh2OKw/0n4THtdGKLb6rIwZvwjc1nwO44P98vK5Sk=; b=v/RkZk4vsP3sOB5hBKr24O59ZkGnfX5YcBPIsodU3ZGbR+Q2pA9bB8rr9EOLQWoKvt BGbt4LOeu+FS+dmDrnPAqkriNrJXbHAMnXtXITVFOKbze1Q2Fr+5XmPyZuJBVly+eqNv LsWCjH4RyGFtCCmipq+G9flpDwArNFFeVCtfE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:x-priority:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; b=kAzkUoq27IsnjalY0dIrpJmDyCDKfb7bqekFiJK1DZU+ZxRC60Y8wrURZ7fD6wBeQX +SR/BHA6AmB01NfFLfVkZmBa87LlSIuTHvL0WuTeHnoigUfKfCGhzWuEUjdjhrJSbgzm am2pCL2cDPkfIcUc6wEbeJj+gUlgbR2eJC/Ho= Subject: Re: [MiNT] cookie jar Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Peter Persson X-Priority: 3 In-Reply-To: <000f256d.01d792623aaa@smtp.freeola.net> Date: Thu, 30 Sep 2010 00:09:47 +0200 Cc: Miro Kropacek , Message-Id: <97B1925C-546F-4764-B811-431DA9BEACB6@gmail.com> References: <000f256d.01d792623aaa@smtp.freeola.net> To: Peter Slegg X-Mailer: Apple Mail (2.1081) X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: pep.fishmoose@gmail.com Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id o8TMC9P3015852 29 sep 2010 kl. 22.22 skrev Peter Slegg: > There is no shame in having bugs in code but people are too keen to > blame 10 year old apps that work fine on 6 versions of TOS, 6 versions > of Magic and dozens of versions of Mint. I quote you: "What actually manages the cookie jar ? Is it the kernel or AES? Where is this error alert coming from ?" If you don't know this already, who are you to make assumptions about this stuff? The cookie jar is managed by every single application that touches it. That's what Atari gave us. It's a really crappy solution. This means every single app that use the cookie jar can potentially screw it up. And it's been known to happen. For example, when the cookie jar is full, applications are required to make a new larger one. Isn't it possible, or even plausible, that some application fails when it's faced with this particular scenario? It also means the problem only manifests itself under certain conditions. So the logical thing is that you disable stuff and see what happens. Find the conditions required to reproduce the problem. And again, a bug can definitely manifest itself even though it hasn't done so for 6 versions of TOS, 6 versions of Magic, and dozens of versions of Mint. > Who complained ? Once again I repeat, I reported an issue and asked > if anyone had seen anything like it. Then you were given some good advice as to how to approach the problem. -- PeP