On Fri, Aug 07, 2009 at 08:16:02PM +0000, corvid wrote:
Jorge wrote:
On Thu, Aug 06, 2009 at 05:20:04AM +0000, corvid wrote:
Jorge wrote:
On Sun, Aug 02, 2009 at 01:40:17PM -0400, Jorge Arellano Cid wrote:
As said in CCCwork.txt it would be good to build the whole chain in one single step (for simplicity) and to define a standard way to end/abort the CCC (which I've given some thought). If muses decide to pay me a visit, I may develop a patch for this soon. :-)
Good news.
I already have dillo running on CCCs that build in one step (both for HTTP and DPI), and also updated the documentation. It's quite stable and behaves very well. Now I have to think what to do with the gained simplicity. :)
Something isn't working right in the new code for Abort.
If I type "dillo http://laskflsjsdfsf" and then ^Q after it fails to resolve, I get a segfault.
(interestingly, if I start dillo with no args [my start url is about:blank] and then try to go to http://laskflsjsdfsf , ^Q just gets me ** WARNING **: CCC: call on already finished chain.)
[...] Now after dns resolution times out, retrying in a new window/tab doesn't seem to work.
Please try the current tip. It's not definitive, but it looks like with some API polish it may be.
Oh, there still is a bug after all.
Yes, it's the same bug BTW. I added a new function call to the CCC API (wrapping the trick of the previous patch) and used it in three parts of the code. Please check the tip.
If I'm not connected and I try to go to a host that I have listed in /etc/hosts, then ^Q gives me a segfault.
Another SEGFAULT path was: load dillo home disconnect Internet click 9years press stop All of these should be working now. Please report any further problem you find. I'll try to make the empty cache entries removal now, and then look for a way to hook the concurrent connection limit without memory leaks. -- Cheers Jorge.-