Hi all,
during the past few days I've started actually implementing the
StringNg class.
I've come across a fundamental design choice, which I'd like to share
with you before I take the completely wrong direction.
The issue is the interaction between buffers, strings and encodings.
Hi list,
Is there any plans to port storeurl directives from 2.7 to 3.x? I
don't see it in 3.1 beta. One of my plugins (intelligentmirror [1])
depends on it. I am not able to release a version for squid-3.x and most
the distros are shipping squid-3.x now.
[1]
On Sat, 2008-12-13 at 14:10 +0100, kinkie wrote:
The issue is the interaction between buffers, strings and encodings.
There's two possibilities:
1- a StringNg holds a Buf and references an Encoding. It's thus blob-ish
and transcoding is done on demand.
Advantages: transcoding is done done
On Sun, Dec 14, 2008 at 6:28 AM, Alex Rousskov
rouss...@measurement-factory.com wrote:
On Sat, 2008-12-13 at 14:10 +0100, kinkie wrote:
The issue is the interaction between buffers, strings and encodings.
There's two possibilities:
1- a StringNg holds a Buf and references an Encoding. It's
