The only thing that would cause "onend" to not be invoked is if the "end" instruction for the stream is never sent (which is unlikely). If you can confirm that normal Guacamole downloads the file as expected, then something else is likely happening here.
Are you positive it's not being invoked? Could there me some other reason that the functionality within your onend handler is not behaving as expected? Any errors in the browser JavaScript console? - Mike On May 17, 2017 11:14, "odonya" <[email protected]> wrote: We have a problem in our guacamole client implementation such that we are not receiving onend notification when trying to read the guacamole stream. Our code snippet looks like this guac = new Guacamole.Client( tunnel ); This is how we are listening on onfile when we are trying to print file. guac.onfile = function clientFileReceived(stream, mimetype, filename) { //this is called var blobReader = new Guacamole.BlobReader(stream, mimetype); blobReader.onend = function onend() { //this is never called } } My question is why is onend not being called? I am using 0.9.12-incubating version of guacamole. -- View this message in context: http://apache-guacamole- incubating-users.2363388.n4.nabble.com/We-have-a-problem- in-our-guacamole-client-implementation-such-that-we-are-not-receiving-onend- notifi-tp974.html Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.
