Re: TCP Connection Semantics

2011-10-04 Thread Nick Kew
On Tue, 04 Oct 2011 09:49:46 -0600 Leif Hedstrom wrote: > On 10/04/2011 07:11 AM, Nick Kew wrote: > > I'd like to write a plugin that works on TCP Connection data. > > In HTTPD I'd just work with the conn_rec and write > > connection-level filters. > > > > TS API exposes HTTP SSN and HTTP TXN, wh

Re: TCP Connection Semantics

2011-10-04 Thread Leif Hedstrom
On 10/04/2011 07:11 AM, Nick Kew wrote: I'd like to write a plugin that works on TCP Connection data. In HTTPD I'd just work with the conn_rec and write connection-level filters. TS API exposes HTTP SSN and HTTP TXN, whose semantics confuse me. Tracing callbacks for them over a simple HTTP requ

server-transform.c patch

2011-10-04 Thread Otto van der Schaaf
Hi, While playing around with the server-transform plugin example, i noticed it was broken. After some meddling around, i got it working again. The changes are mainly that in some cases content-length was passed in network-byte order where it shouldn't be. Another fix was handling the TS_EVENT_IMM

TCP Connection Semantics

2011-10-04 Thread Nick Kew
I'd like to write a plugin that works on TCP Connection data. In HTTPD I'd just work with the conn_rec and write connection-level filters. TS API exposes HTTP SSN and HTTP TXN, whose semantics confuse me. Tracing callbacks for them over a simple HTTP request, I get the order of callbacks: SSN S

Re: t/r 3.0.2

2011-10-04 Thread Jim Jagielski
Should we set some deadline? I can RM if need be. On Oct 3, 2011, at 2:03 PM, Jim Jagielski wrote: > Gone as far as I can on STATUS… > > On Sep 30, 2011, at 7:20 AM, Jim Jagielski wrote: > >> Will look today… Not sure if I'll have time to do the actual >> commits but will be able to at least fi

Re: Bug triage for v3.1.1 and v3.1.2

2011-10-04 Thread Jim Jagielski
I should, but just in case, can you ensure I do :) On Oct 3, 2011, at 4:34 PM, Leif Hedstrom wrote: > On 10/03/2011 02:07 PM, Leif Hedstrom wrote: >> Hi all, >> >> there are 100 bugs open for v3.1.1 and 75 for v3.1.2. We need to triage this >> :). Please, everyone, take a look at all these bugs