- Dillo-dev - lists.mailman3.com

display: inline

by jcid＠dillo.org

On Tue, Jan 19, 2010 at 08:17:01PM +0100, Johannes Hofmann wrote: > On Mon, Jan 18, 2010 at 03:40:31PM -0300, Jorge Arellano Cid wrote: > > On Tue, Jan 12, 2010 at 06:48:19PM +0100, Johannes Hofmann wrote: > > > On Tue, Dec 08, 2009 at 06:56:55PM +0100, Johannes Hofmann wrote: > > > > Hi, > > > > > > > > I started to experiment with the real solution, which means that the > > > > display member of Style determines whether a (Text)block is created > > > > or a ListItem, or whether just normal text is added. > > > > The patch is still small, but as the change is pretty > > > > fundamental, so I decided to put it in a separate repo for now. > > > > You can find it at: > > > > > > > > http://www.flpsed.org/hgweb/dillo_display/ > > > > > > > > > > I've updated this prototype a bit. It works quite well, the only > > > drawback is the added complexity in html.cc. > > > In addition to Html_tag_open_*() and Html_tag_clone_*(), there now is > > > an optional Html_tag_content_*() function for tags that create > > > widgets or other content. This function is not called in the > > > display:none case. > > > The reason for the splitting into Html_tag_open_*() and > > > Html_tag_content_*() is that styleEngine->setNonCssHints() is > > > needed before we can get the current style. > > > Only after that is done, we know the value of the display property > > > and can decide whether to call Html_tag_content_*() or not. > > > > > > I'd like to get this into main line soon if you agree. > > > Please let me know what you think. > > > [...] > > - Please don't merge the IPPROTO_TCP patch with it. > > If you mean the TCP_NODELAY stuff, it's in the main repo already. > Normally the TCP stack waits a little until there is enough data to > send. This is good for throughput but bad for response time. It is > especially bad for client server stuff like DPI over local loopback. > It really slows down pages with cookies. > But I can back it out if you like. It would no longer be necessary > when we switch back to UNIX domain sockets anyway. OK, leave it then. BTW, is the connection-number-limit patch in the next release? -- Cheers Jorge.-

Jan. 20, 2010

experimental patch: gnutls for the https dpi

by corvid＠lavabit.com

A few hours ago, I started to wonder how much trouble it would be to make https.c understand gnutls instead of openssl. The answer is: If you borrow liberally from the public domain code in the gnutls manual, then not very much! So here's a toy for anyone who would like one: http://www.dillo.org/test/gnutls.0.patch Now we'll _have_ to have a release soon, because we're accumulating so many things to play with after release...

Jan. 20, 2010

display: inline

by Johannes.Hofmann＠gmx.de

On Mon, Jan 18, 2010 at 03:40:31PM -0300, Jorge Arellano Cid wrote: > On Tue, Jan 12, 2010 at 06:48:19PM +0100, Johannes Hofmann wrote: > > On Tue, Dec 08, 2009 at 06:56:55PM +0100, Johannes Hofmann wrote: > > > Hi, > > > > > > I started to experiment with the real solution, which means that the > > > display member of Style determines whether a (Text)block is created > > > or a ListItem, or whether just normal text is added. > > > The patch is still small, but as the change is pretty > > > fundamental, so I decided to put it in a separate repo for now. > > > You can find it at: > > > > > > http://www.flpsed.org/hgweb/dillo_display/ > > > > > > > I've updated this prototype a bit. It works quite well, the only > > drawback is the added complexity in html.cc. > > In addition to Html_tag_open_*() and Html_tag_clone_*(), there now is > > an optional Html_tag_content_*() function for tags that create > > widgets or other content. This function is not called in the > > display:none case. > > The reason for the splitting into Html_tag_open_*() and > > Html_tag_content_*() is that styleEngine->setNonCssHints() is > > needed before we can get the current style. > > Only after that is done, we know the value of the display property > > and can decide whether to call Html_tag_content_*() or not. > > > > I'd like to get this into main line soon if you agree. > > Please let me know what you think. > > I checked the last repo, and AFAIS it's OK to merge. I agreed with corvid to leave it out until after the release. > > Notes: > > - I agree with corvid on using NULL instead of Html_tag_close_default. Ok. > - There's a comment on *open and *close() function being always > called but there's still a conditional close on display_none. > Please check it. Ok. > - Please don't merge the IPPROTO_TCP patch with it. If you mean the TCP_NODELAY stuff, it's in the main repo already. Normally the TCP stack waits a little until there is enough data to send. This is good for throughput but bad for response time. It is especially bad for client server stuff like DPI over local loopback. It really slows down pages with cookies. But I can back it out if you like. It would no longer be necessary when we switch back to UNIX domain sockets anyway. Cheers, Johannes

Jan. 19, 2010

dillo2.x on Fedora 12

by newman.x＠gmail.com

On Mon, Jan 18, 2010 at 9:17 PM, Globe Trotter <itsme_410(a)yahoo.com> wrote: > Hi, > > Does that mean that Dillo has no hope also because it is based on fltk2? > > Thanks! > T FLTK2 is somewhat dead end from Fedora perspective. There is a bunch of issues in upstream FLTK2 snapshots regarding Fedora package policies. I fixed several of them in Package Review https://bugzilla.redhat.com/show_bug.cgi?id=fltk2 but then lost hope when others appeared... And more, upstream's not willing to fix bugs I found when pushing FLTK2 to Fedora (e.g. they sticked w/ "static" linking). FLTK1.3 (and 1.4) is the way to go, once it's released. I remember, release was scheduled for last summer but postponed. See their mailing list for latest info, they have some 4 items, 2 of them non-trivial, on the list. Michal

Jan. 19, 2010

Cookies performance

by furaisanjin＠gmail.com

2010/1/19 Johannes Hofmann <Johannes.Hofmann(a)gmx.de>: > Do you have a fast or slow internet connection? I have FTTH at home and the connection iself is quite fast. > Do you know what kind of proxy you are connecting to? I'm using this proxy on my machine. <<http://www.acme.com/software/micro_proxy/>> But I modified this to act as daemon and limit the active connection (usually the active connection limit is 4 but proxy itself accepts all connections). I found that my modification for the proxy caused the problem. I had to modify a_Capi_stop_client like this. Client = a_Cache_client_get_if_unique(Key); - if (Client && (force || Client->BufSize == 0)) { + if (Client && force) { /* remove empty entries too */ a_Capi_conn_abort_by_url(Client->Url); After I canceled my modification, downloading didn't stop but I started seeing this kind of warning. ** WARNING **: IO_write, closing with pending data not sent ** WARNING **: "GET http://img.f.hatena.ne.jp/images/fotolife/z/zankuro/20090805/20090805082105… HTTP/1.1\x0D Regards, furaisanjin

Jan. 19, 2010

Cookies performance

by Johannes.Hofmann＠gmx.de

On Mon, Jan 18, 2010 at 06:59:08PM +0100, Johannes Hofmann wrote: > On Mon, Jan 18, 2010 at 03:58:25PM +0900, furaisanjin wrote: > > 2010/1/18 Johannes Hofmann <Johannes.Hofmann(a)gmx.de>: > > > Please test attached patch. It limits the overall number of > > > concurrent connections to 4. > > > > I tested this with TCP_NODELAY option and it seems that further image > > downloading stops when the page repush happens due to remote CSS. So I > > don't see all images. Good thing is that I don't get the error > > message. > > Hm, it seems to work ok here... Ok, I'm also seeing an issue now. Not sure if it's the problem you are having. With an overall limit of open connections a slow server can eat up all 4 connections. Then dillo can't connect to other hosts anymore, e.g. in an other window or tab. This needs to be addressed.

Jan. 19, 2010

dillo2.x on Fedora 12

by Johannes.Hofmann＠gmx.de

On Mon, Jan 18, 2010 at 12:17:08PM -0800, Globe Trotter wrote: > > > --- On Fri, 12/18/09, Michal Nowak <newman.x(a)gmail.com> wrote: > > > From: Michal Nowak <newman.x(a)gmail.com> > > Subject: Re: [Dillo-dev] dillo2.x on Fedora 12 > > To: "Globe Trotter" <itsme_410(a)yahoo.com> > > Cc: dillo-dev(a)dillo.org > > Date: Friday, December 18, 2009, 6:26 AM > > On Fri, Dec 18, 2009 at 4:47 AM, > > Globe Trotter <itsme_410(a)yahoo.com> > > wrote: > > > Hi, > > > > > > Any likelihood of getting some Fedora 12 dillo2 RPMS? > > > > > > > You may try > > > > http://mnowak.fedorapeople.org/dillo2/ > > > > should be the last release. There are static RPMs for F-11 > > and SRPM, which > > you can rebuild yourself for F-12, when you have installed > > static FLTK2 > > > > http://mnowak.fedorapeople.org/fltk2/static/ > > > > Though, unlikely to have Dillo 2 in Fedora as a supported > > package due to > > FLTK2, which is used in Dillo 2, is unreleased version, we > > don't wanna in > > Fedora. (Anyway FLTK2 seemed to me dead, last time I've > > looked, anyway.) > > Hi, > > Does that mean that Dillo has no hope also because it is based on fltk2? Definately not. Even though there is only few development going on for fltk2, it works rather well for us and pressing bugs get fixed. We also keep an eye on fltk-1.3 for which there is active development. Once there is an official fltk-1.3 release we will consider whether to switch to that version. Generally in dillo2 there is a pretty good separation of general code and GUI toolkit dependent code, so a port to another toolkit is possible. Cheers, Johannes

Jan. 18, 2010

dillo2.x on Fedora 12

by Johannes.Hofmann＠gmx.de

On Mon, Jan 18, 2010 at 12:17:08PM -0800, Globe Trotter wrote: > > > --- On Fri, 12/18/09, Michal Nowak <newman.x(a)gmail.com> wrote: > > > From: Michal Nowak <newman.x(a)gmail.com> > > Subject: Re: [Dillo-dev] dillo2.x on Fedora 12 > > To: "Globe Trotter" <itsme_410(a)yahoo.com> > > Cc: dillo-dev(a)dillo.org > > Date: Friday, December 18, 2009, 6:26 AM > > On Fri, Dec 18, 2009 at 4:47 AM, > > Globe Trotter <itsme_410(a)yahoo.com> > > wrote: > > > Hi, > > > > > > Any likelihood of getting some Fedora 12 dillo2 RPMS? > > > > > > > You may try > > > > http://mnowak.fedorapeople.org/dillo2/ > > > > should be the last release. There are static RPMs for F-11 > > and SRPM, which > > you can rebuild yourself for F-12, when you have installed > > static FLTK2 > > > > http://mnowak.fedorapeople.org/fltk2/static/ > > > > Though, unlikely to have Dillo 2 in Fedora as a supported > > package due to > > FLTK2, which is used in Dillo 2, is unreleased version, we > > don't wanna in > > Fedora. (Anyway FLTK2 seemed to me dead, last time I've > > looked, anyway.) > > Hi, > > Does that mean that Dillo has no hope also because it is based on fltk2? Definately not. Even though there is only few development going on for fltk2, it works rather well for us and pressing bugs get fixed. We also keep an eye on fltk-1.3 for which there is active development. Once there is an official fltk-1.3 release we will consider whether to switch to that version. Generally in dillo2 there is a pretty good separation of general code and GUI toolkit dependent code, so a port to another toolkit is possible. Cheers, Johannes

Jan. 18, 2010

Cookies performance

by Johannes.Hofmann＠gmx.de

On Mon, Jan 18, 2010 at 06:19:28PM +0000, corvid wrote: > Johannes wrote: > > On Mon, Jan 18, 2010 at 03:58:25PM +0900, furaisanjin wrote: > > > 2010/1/18 Johannes Hofmann <Johannes.Hofmann(a)gmx.de>: > > > > Please test attached patch. It limits the overall number of > > > > concurrent connections to 4. > > > > > > I tested this with TCP_NODELAY option and it seems that further image > > > downloading stops when the page repush happens due to remote CSS. So I > > > don't see all images. Good thing is that I don't get the error > > > message. > > > > Hm, it seems to work ok here... > > > > Does loading other pages still work, after image loading has > > stalled, or is the complete dillo instance broken after that? > > > > Do you have a fast or slow internet connection? > > > > Do you know what kind of proxy you are connecting to? > > I've tried with image loading and remote stylesheets on to the > degree that I can tolerate :) , and I like this connection > limiting a whole lot. We definately need a connection limit. Currently dillo can be spawning hundreds of connections to a single server which is not nice. HTTP 1.1 even suggests a limit of 2 connections per host though according to http://www.stevesouders.com/blog/2008/03/20/roundup-on-parallel-connections/ modern browsers us something between 2 and 6 now, so I think an overall limit of 4 is ok for dillo. There even is a benefit when loading long pages with images: With the connection limit in place the first (and probabely visible) images on the page get more bandwidth and load faster. > > So far, all I've noticed was once getting one of those > "IO_write, closing with pending data not sent" msgs > when I left a page while things were loading. It didn't seem > to cause any harm, though. > This might be connections that get aborted while still queued and therefore not connected. I will check that. Cheers, Johannes

Jan. 18, 2010

dillo2.x on Fedora 12

by itsme_410＠yahoo.com

--- On Fri, 12/18/09, Michal Nowak <newman.x(a)gmail.com> wrote: > From: Michal Nowak <newman.x(a)gmail.com> > Subject: Re: [Dillo-dev] dillo2.x on Fedora 12 > To: "Globe Trotter" <itsme_410(a)yahoo.com> > Cc: dillo-dev(a)dillo.org > Date: Friday, December 18, 2009, 6:26 AM > On Fri, Dec 18, 2009 at 4:47 AM, > Globe Trotter <itsme_410(a)yahoo.com> > wrote: > > Hi, > > > > Any likelihood of getting some Fedora 12 dillo2 RPMS? > > > > You may try > > http://mnowak.fedorapeople.org/dillo2/ > > should be the last release. There are static RPMs for F-11 > and SRPM, which > you can rebuild yourself for F-12, when you have installed > static FLTK2 > > http://mnowak.fedorapeople.org/fltk2/static/ > > Though, unlikely to have Dillo 2 in Fedora as a supported > package due to > FLTK2, which is used in Dillo 2, is unreleased version, we > don't wanna in > Fedora. (Anyway FLTK2 seemed to me dead, last time I've > looked, anyway.) Hi, Does that mean that Dillo has no hope also because it is based on fltk2? Thanks! T > Unless Dillo 2 is based on some released and supported > toolkit, Dillo 2 won't > be Fedora-supported.

Jan. 18, 2010