Can anyone please let us know if there are any issues in calling the 'TSVConnWrite' api multiple times (with 4th argument equal to content length) as i pointed in my previous reply ?
On Tue, Jul 4, 2017 at 9:43 AM, Gaurav Bansal <[email protected]> wrote: > Thanks Nick for the reply. I am using following code but still the > behaviour remains the same : > > > > > > *if (!data->output_vio) { data->output_vio = > TSVConnWrite(TSTransformOutputVConnGet(contp), contp, data->output_reader, > TSVIONBytesGet(write_vio)); TSVIONBytesSet(data->output_vio, > TSVIONBytesGet(write_vio));}* > The above code is used, when we have just got the first packet from the > upstream (server-side) connection & no data has yet been sent to the > client. And as and when we keep getting packets, we keep on sending them to > the client (after performing some checks) using the following api : > > TSVConnWrite(TSTransformOutputVConnGet(contp), contp, > data->output_reader, data->content_length); > > Still we don't get any TS_EVENT_VCONN_WRITE_COMPLETE event. Any idea on > what might be going wrong ? What else can be tried ? > > On Mon, Jul 3, 2017 at 1:32 PM, Nick Kew <[email protected]> wrote: > >> On Mon, 2017-07-03 at 09:19 +0530, Gaurav Bansal wrote: >> > When the transaction is finished, we call the below api : >> > TSContCall(TSVIOContGet(write_vio), TS_EVENT_VCONN_WRITE_COMPLETE, >> > write_vio); >> >> Is it possible your downstream is still expecting more data? >> You might want to be sure you've got it right by setting >> NBytes on your VIO at this point. >> >> -- >> Nick Kew >> >> >> >
