Changes

Jump to navigation Jump to search
233 bytes removed ,  20:05, 7 June 2018
no edit summary
* <code>%rest:single</code> annotation to cancel running RESTXQ functions
* Quality factors in the [[#Content Negotiation|Accept header]] will be evaluated
* {{Version|9.0}}: Support for server-side quality factors in the [[#Content Negotiation|<code>%rest:produces</code>]] annotation
<br />
…and if two RESTXQ functions exist with the same {{Code|path}} annotation, one with the {{Code|produces}} annotation <code>*/*</code>, and another with <code>text/html</code>, the second function will be called, because the quality factor for <code>text/html</code> documents is highest.
With {{Version|9.0}}, support for serverServer-side quality factors was added. are supported as well: If multiple function candidates are left over after the above steps, the <code>qs</code> parameter will be considered. The function with the highest quality factor will be favored:
<pre class="brush:xquery">
==Query Execution==
 
{{Mark|Updated with Version 9.0:}} The old status code {{Code|410}} (which indicates to the client that a resource is permanently removed) was replaced with {{Code|460}}.
In many RESTXQ search scenarios, input from browser forms is processed and search results are returned. User experience can generally be made more interactive if an updated search request is triggered with each key click. However, this may lead to many expensive parallel requests, from which only the result of the last request will be relevant for the client.
declare %rest:path("") function page:error404() {
<rest:response>
<http:response status="404" reasonmessage="I was not found.">
<http:header name="Content-Language" value="en"/>
<http:header name="Content-Type" value="text/html; charset=utf-8"/>
=User Authentication=
If you want to provide restricted access to parts of a web applications, you will need to check permissions before returning a response to the client. With {{Version|9.0}} of BaseX, a The [[Permissions]] layer was introduced to facilitate is a nice abstraction for defining permission checks.
=Functions=
Bureaucrats, editor, reviewer, Administrators
13,550

edits

Navigation menu