S
slacroixak
Guest
Dear forum, doing with 11.7.5 In a recent thread about sending a large binary file to an AppServer, I was advised to adopt the Web transport with WebHandlers. At a point I thought I might first compress my file before sending it. Now that I am about doing it, I recall http has native compression capabilities... This KBase says how to enable compression for the REST Transport : Progress KB - How to enable HTTP Compression for an OpenEdge REST web application ? Q0 : Having played with different levels of compression with 7zip, I found out the default compression rate was a good compromise between the time it takes to make it and the obtained compression. Based on that, would you rather compress your file locally before sending a zipped version of it, or would just rely on the native compression capabilities of http to do it on the fly, hoping it would negotiate the rate adaptively? Q1 : I suppose the KBase works for the WEB transport as well as ofr REST, correct? Q2 : How about the APSV transport? Does Tomcat enable compression for it as well ? Q3 : Does the -mc startup parameter work for the PASOE, or does it apply only for the old classical AppServer? Q4: Aside, with the APSV transport and the Classic AppServer, I do not recall if we can send a MEMPTR to an AppServer session (it may make no sense...) and cannot find it in the Doc. If it is possible, would it better to send a large binary message with APSV transport and a MEMPTR param with -mc, or with the WEB transport with the enable compression mechanism described in the KBase?
Continue reading...
Continue reading...