[naviserver-devel] ns_chan and ns_connchan

2017-04-07 Thread Wolfgang Winkler
Hi! We have some long running scripts, e.g. shrinking of large PDF files, and want to prevent reverse proxy and browser timeouts. To achieve this, we are trying to periodically send small packages from the server to the browser while these scripts are running. First we tried with ns_conn an

Re: [naviserver-devel] ns_chan and ns_connchan

2017-04-07 Thread David Osborne
Re the first issue, I only have experience of ns_connchan but I believe the situation is the same. You can specify r,w,e, or x for the *argument* ?when? upon creation of the callback, but the callback will be triggered upon timeout with a *value* of $when = "t" regardless of what you specify as th

Re: [naviserver-devel] ns_chan and ns_connchan

2017-04-07 Thread Wolfgang Winkler
I'm trying to write out html code or javascript code fragments to show the progress of the operations. Am 2017-04-07 um 10:57 schrieb David Osborne: Re the first issue, I only have experience of ns_connchan but I believe the situation is the same. You can specify r,w,e, or x for the *argument*

Re: [naviserver-devel] ns_chan and ns_connchan

2017-04-07 Thread David Osborne
We seem to be able to write happily to a connchan channel directly using a string representation as follows eg. ns_connchan write $to "HTTP/1.0 504 Gateway Timout\r\n\r\n" This is a guess, but could you be forcing an implicit type conversion of your string by manipulating it with non-bytearray a

Re: [naviserver-devel] revproxy timeouts

2017-04-07 Thread Gustaf Neumann
Hi David, thanks for testing! I think, i have fixed the problem with: https://bitbucket.org/naviserver/naviserver/commits/221d0c8f629bb29235e156a781ca5599284c3e9d The bug was a problem in nsssl triggered by "ns_connchan close". The same verison of revproxy should work. all the best -g Am 06.

Re: [naviserver-devel] revproxy timeouts

2017-04-07 Thread David Osborne
Spot on - that works great - thanks! On 7 April 2017 at 16:01, Gustaf Neumann wrote: > Hi David, > > thanks for testing! > I think, i have fixed the problem with: > > https://bitbucket.org/naviserver/naviserver/commits/ > 221d0c8f629bb29235e156a781ca5599284c3e9d > > The bug was a problem in