Question on keeping transactions alive to see the total file

[Robert Logue <ro...@openwave.com>]

Hello,

In certain situations my plugin has to see the total file that the 
client requests, even if the client ends the transaction before the 
download is complete. This needs to be done on a per transaction basis.

I was told that

/|proxy.config.http.background_fill_active_timeout|/
/|proxy.config.http.background_fill_completed_threshold|/

will help me do this, though TS would need to be modified to allow me to 
set these on a per transaction basis. Also for these values to work I 
need to have caching enabled for the transaction.

So my questions are: are there any documents on how to set up caching on 
a per transaction basis? Will it be difficult to modify TS to allow me 
to set background_fill* on a per transaction basis?

Or is this the best approach to solve my problem?

Thanks

Robert

Re: Question on keeping transactions alive to see the total file

[Igor Galić <i....@brainsware.org>]

>   * It is extremely easy to modify TS to allow a plugin to alter the
>     background fill config values on a per transaction basis. I am
>     going
>     to provide a patch to TS so this should be available after that
>     has
>     been accepted.

w00t \o/

> That's it.
> 
> Robert
> 
> 

-- 
Igor Galić

Tel: +43 (0) 664 886 22 883
Mail: i.galic@brainsware.org
URL: http://brainsware.org/
GPG: 6880 4155 74BD FD7C B515  2EA5 4B1D 9E08 A097 C9AE

Re: Question on keeping transactions alive to see the total file

[Robert Logue <ro...@openwave.com>]

On 16/04/12 09:43, Robert Logue wrote:
> Hello,
>
> In certain situations my plugin has to see the total file that the 
> client requests, even if the client ends the transaction before the 
> download is complete. This needs to be done on a per transaction basis.
>
> I was told that
>
> /|proxy.config.http.background_fill_active_timeout|/
> /|proxy.config.http.background_fill_completed_threshold|/
>
> will help me do this, though TS would need to be modified to allow me 
> to set these on a per transaction basis. Also for these values to work 
> I need to have caching enabled for the transaction.
>
> So my questions are: are there any documents on how to set up caching 
> on a per transaction basis? Will it be difficult to modify TS to allow 
> me to set background_fill* on a per transaction basis?
>
> Or is this the best approach to solve my problem?
>
> Thanks
>
> Robert
>
>

I got a few response to this on the IRC channel so I will just summarise 
here the information I got.

  * Background fill is the best way to keep a transaction alive to allow
    a transformation to see the total file
  * Caching does need to be enabled to allow this feature to work
  * Caching can be enabled by various methods one being adding a
    Cache-Control:max-age header with a suitably large value.
  * It is extremely easy to modify TS to allow a plugin to alter the
    background fill config values on a per transaction basis. I am going
    to provide a patch to TS so this should be available after that has
    been accepted.


That's it.

Robert