Alan:
I think we have make many effort on this issue already, and fairly
sure that we are closing to the root cause of it. From my team side,
we'd like to keep tracking it instead of hiding the issue. please
holding back the commit, and give us more detail on the crashing back
traces as much as p
Here are my comments for what they are worth.
First, let me detail the issue this is trying to address.
The way that most clients work with VCs is via and Processor::open_
which calls back with and OPEN event at which point they set VIOs mutex
field and from this point on, access to the VC is
Hi all,
I just committed support for the Server Name Indication TLS extension to trunk.
There's no additional configuration necessary. When we load any certificate, we
will automatically parse the subject CN and all the alternate DNS names and
match them when requested. All you have to do is ma
Great, thanks Igor and Leif.
Brian
2012/3/13 Igor Galić
>
>
> - Original Message -
> > On 3/13/12 2:06 PM, Brian Geffon wrote:
> > > Hi,
> > > Is there anyway to pass configuration data to a plugin on a per
> > > remap rule
> > > basis? I'm looking to have the configuration that a remap
- Original Message -
> On 3/13/12 2:06 PM, Brian Geffon wrote:
> > Hi,
> > Is there anyway to pass configuration data to a plugin on a per
> > remap rule
> > basis? I'm looking to have the configuration that a remap plugin
> > provides
> > but on top of a full plugin.
> >
> > Does anyone
On 3/13/12 2:06 PM, Brian Geffon wrote:
Hi,
Is there anyway to pass configuration data to a plugin on a per remap rule
basis? I'm looking to have the configuration that a remap plugin provides
but on top of a full plugin.
Does anyone have ideas?
Take a look at the header_filter plugin. It do
Hi,
Is there anyway to pass configuration data to a plugin on a per remap rule
basis? I'm looking to have the configuration that a remap plugin provides
but on top of a full plugin.
Does anyone have ideas?
Thanks.
Brian
I have a patch submitted for TS-857 which attempts to make a start on finer
grained locking. The essence of it is
1) Provide more powerful and standards compliant reference counted smart
pointers - lib/ts/IntrusivePtr.h
2) Provide reference counted lists that are compatible with both (1) and
e