Main Page » Mailing List » November 2016

Restxq handling accept-encoding

Wednesday, 16 November 2016 · 6 messages · last reply 18 Nov 2016
KS
Kendall Shaw16 Nov 2016 01:58 #
To return compressed text data, should I explicitly look for Accept-Encoding and use java to deflate or gzip output of convert:binary-to-string(db:retrieve(…))? Kendall
KS
Kendall Shaw16 Nov 2016 02:29 #
I should clarify that I’m asking about content negotiation. %rest:produces is described as constraining based on the Accept header. Should I explicitly look for Accept-Encoding and produce binary data that is in one of the requested compressed formats, or is there something in basex’s restxq implementation that does this? Kendall
Quoted text · Kendall Shaw · 6 lines
From: <basex-talk-bounces at mailman.uni-konstanz.de> on behalf of Kendall Shaw <kendall.shaw at workday.com> Date: Tuesday, November 15, 2016 at 4:58 PM To: BaseX <basex-talk at mailman.uni-konstanz.de> Subject: [basex-talk] Restxq handling accept-encoding To return compressed text data, should I explicitly look for Accept-Encoding and use java to deflate or gzip output of convert:binary-to-string(db:retrieve(…))? Kendall
CG
Christian Grün16 Nov 2016 10:45 #
Hi Kendall, This is usually handled by the web server (by default, Jetty). Maybe this helps? http://blog.max.berger.name/2010/01/jetty-7-gzip-filter.html Cheers, Christian
Quoted text · Kendall Shaw · 30 lines
On Wed, Nov 16, 2016 at 2:29 AM, Kendall Shaw <kendall.shaw at workday.com> wrote: > I should clarify that I’m asking about content negotiation. %rest:produces > is described as constraining based on the Accept header. Should I explicitly > look for Accept-Encoding and produce binary data that is in one of the > requested compressed formats, or is there something in basex’s restxq > implementation that does this? > > > > Kendall > > > > From: <basex-talk-bounces at mailman.uni-konstanz.de> on behalf of Kendall Shaw > <kendall.shaw at workday.com> > Date: Tuesday, November 15, 2016 at 4:58 PM > To: BaseX <basex-talk at mailman.uni-konstanz.de> > Subject: [basex-talk] Restxq handling accept-encoding > > > > To return compressed text data, should I explicitly look for Accept-Encoding > and use java to deflate or gzip output of > convert:binary-to-string(db:retrieve(…))? > > > > Kendall > >
KS
Kendall Shaw16 Nov 2016 19:35 #
Thank you. I’m using tomcat, not for any particular reason. There I added: compression=”on” compressableMimeType="text/html,text/xml,text/plain,text/css,text/javascript,application/javascript,application/json" to the connector element in server.xml. For now, that’s good enough. Eventually, I’ll want to figure out how to store a compressed resource and serve that if compression is request. Kendall
Quoted text · Christian Grün · 1 line
On 11/16/16, 1:45 AM, "Christian Grün" <christian.gruen at gmail.com> wrote:
Hi Kendall, This is usually handled by the web server (by default, Jetty). Maybe this helps? https://urldefense.proofpoint.com/v2/url?u=http-3A__blog.max.berger.name_2010_01_jetty-2D7-2Dgzip-2Dfilter.html&d=DgIFaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=JgwnBEpN1c-DDmq-Up2QMq9rrGyfWK0KtSpT7dxRglA&m=6JsUJinjuwLxS__1HSp55O2G4zm8DoUtTk-zEVzV8cQ&s=ZWuB0REriC5VtRp4dTHd-HoaJ70qXUAVfj49wV_AggI&e= Cheers, Christian
Quoted text · Kendall Shaw · 30 lines
On Wed, Nov 16, 2016 at 2:29 AM, Kendall Shaw <kendall.shaw at workday.com> wrote: > I should clarify that I’m asking about content negotiation. %rest:produces > is described as constraining based on the Accept header. Should I explicitly > look for Accept-Encoding and produce binary data that is in one of the > requested compressed formats, or is there something in basex’s restxq > implementation that does this? > > > > Kendall > > > > From: <basex-talk-bounces at mailman.uni-konstanz.de> on behalf of Kendall Shaw > <kendall.shaw at workday.com> > Date: Tuesday, November 15, 2016 at 4:58 PM > To: BaseX <basex-talk at mailman.uni-konstanz.de> > Subject: [basex-talk] Restxq handling accept-encoding > > > > To return compressed text data, should I explicitly look for Accept-Encoding > and use java to deflate or gzip output of > convert:binary-to-string(db:retrieve(…))? > > > > Kendall > >
KS
Kendall Shaw18 Nov 2016 08:20 #
So, to avoid having the web server compress content at runtime, it appears that I can do this: declare %rest:path('/test-binary') %rest:GET function w:test-binary() { web:response-header(map {'media-type': 'application/json'}, map {'Content-Encoding': 'gzip'}) , db:retrieve('test-binary', 'out.bin') }; where out.bin contains gzipped json text. I would then serve the gzipped resource if Accept-Encoding contains deflate or gzip and otherwise serve the text resource. Is there any problem with that approach? Kendall
Quoted text · basex-talk-bounces at mailman.uni-konstanz.de on behalf of Kendall Shaw · 1 line
On 11/16/16, 10:35 AM, "basex-talk-bounces at mailman.uni-konstanz.de on behalf of Kendall Shaw" <basex-talk-bounces at mailman.uni-konstanz.de on behalf of kendall.shaw at workday.com> wrote:
Thank you. I’m using tomcat, not for any particular reason. There I added: compression=”on” compressableMimeType="text/html,text/xml,text/plain,text/css,text/javascript,application/javascript,application/json" to the connector element in server.xml. For now, that’s good enough. Eventually, I’ll want to figure out how to store a compressed resource and serve that if compression is request. Kendall
Quoted text · Christian Grün · 1 line
On 11/16/16, 1:45 AM, "Christian Grün" <christian.gruen at gmail.com> wrote:
Hi Kendall, This is usually handled by the web server (by default, Jetty). Maybe this helps? https://urldefense.proofpoint.com/v2/url?u=http-3A__blog.max.berger.name_2010_01_jetty-2D7-2Dgzip-2Dfilter.html&d=DgIFaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=JgwnBEpN1c-DDmq-Up2QMq9rrGyfWK0KtSpT7dxRglA&m=6JsUJinjuwLxS__1HSp55O2G4zm8DoUtTk-zEVzV8cQ&s=ZWuB0REriC5VtRp4dTHd-HoaJ70qXUAVfj49wV_AggI&e= Cheers, Christian
Quoted text · Kendall Shaw · 30 lines
On Wed, Nov 16, 2016 at 2:29 AM, Kendall Shaw <kendall.shaw at workday.com> wrote: > I should clarify that I’m asking about content negotiation. %rest:produces > is described as constraining based on the Accept header. Should I explicitly > look for Accept-Encoding and produce binary data that is in one of the > requested compressed formats, or is there something in basex’s restxq > implementation that does this? > > > > Kendall > > > > From: <basex-talk-bounces at mailman.uni-konstanz.de> on behalf of Kendall Shaw > <kendall.shaw at workday.com> > Date: Tuesday, November 15, 2016 at 4:58 PM > To: BaseX <basex-talk at mailman.uni-konstanz.de> > Subject: [basex-talk] Restxq handling accept-encoding > > > > To return compressed text data, should I explicitly look for Accept-Encoding > and use java to deflate or gzip output of > convert:binary-to-string(db:retrieve(…))? > > > > Kendall > >
CG
Christian Grün18 Nov 2016 16:28 #
...should work!
Quoted text · Kendall Shaw · 101 lines
Am 18.11.2016 8:20 vorm. schrieb "Kendall Shaw" <kendall.shaw at workday.com>: > So, to avoid having the web server compress content at runtime, it appears > that I can do this: > > declare > %rest:path('/test-binary') > %rest:GET > function w:test-binary() > { > web:response-header(map {'media-type': 'application/json'}, map > {'Content-Encoding': 'gzip'}) > , db:retrieve('test-binary', 'out.bin') > }; > > where out.bin contains gzipped json text. > > I would then serve the gzipped resource if Accept-Encoding contains > deflate or gzip and otherwise serve the text resource. > > Is there any problem with that approach? > > Kendall > > On 11/16/16, 10:35 AM, "basex-talk-bounces at mailman.uni-konstanz.de on > behalf of Kendall Shaw" <basex-talk-bounces at mailman.uni-konstanz.de on > behalf of kendall.shaw at workday.com> wrote: > > Thank you. I’m using tomcat, not for any particular reason. There I > added: > > compression=”on” > compressableMimeType="text/html,text/xml,text/plain,text/ > css,text/javascript,application/javascript,application/json" > > to the connector element in server.xml. For now, that’s good enough. > Eventually, I’ll want to figure out how to store a compressed resource and > serve that if compression is request. > > Kendall > > On 11/16/16, 1:45 AM, "Christian Grün" <christian.gruen at gmail.com> > wrote: > > Hi Kendall, > > This is usually handled by the web server (by default, Jetty). > Maybe this helps? > > https://urldefense.proofpoint.com/v2/url?u=http-3A__blog. > max.berger.name_2010_01_jetty-2D7-2Dgzip-2Dfilter.html&d= > DgIFaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=JgwnBEpN1c-DDmq- > Up2QMq9rrGyfWK0KtSpT7dxRglA&m=6JsUJinjuwLxS__1HSp55O2G4zm8DoUtTk-zEVzV8cQ& > s=ZWuB0REriC5VtRp4dTHd-HoaJ70qXUAVfj49wV_AggI&e= > > Cheers, > Christian > > > > On Wed, Nov 16, 2016 at 2:29 AM, Kendall Shaw < > kendall.shaw at workday.com> wrote: > > I should clarify that I’m asking about content negotiation. > %rest:produces > > is described as constraining based on the Accept header. Should > I explicitly > > look for Accept-Encoding and produce binary data that is in one > of the > > requested compressed formats, or is there something in basex’s > restxq > > implementation that does this? > > > > > > > > Kendall > > > > > > > > From: <basex-talk-bounces at mailman.uni-konstanz.de> on behalf of > Kendall Shaw > > <kendall.shaw at workday.com> > > Date: Tuesday, November 15, 2016 at 4:58 PM > > To: BaseX <basex-talk at mailman.uni-konstanz.de> > > Subject: [basex-talk] Restxq handling accept-encoding > > > > > > > > To return compressed text data, should I explicitly look for > Accept-Encoding > > and use java to deflate or gzip output of > > convert:binary-to-string(db:retrieve(…))? > > > > > > > > Kendall > > > > > > > > >

Written for BaseX 8.5. BaseX may have changed since: please check the current documentation.

« Testing one data directory per tenant"No function found that matches the request, " basexhttp, OS X El Capitan, and brew »
⚡Generated with XQuery