Difference between revisions of "Talk:LSL HTTP server"
Jump to navigation
Jump to search
Maike Short (talk | contribs) |
Maike Short (talk | contribs) |
||
| Line 1: | Line 1: | ||
{{Talk}} | {{Talk}} | ||
== Stable URL == | |||
I am sorry but I fail how this can make any sense without a stable URL. The url could consist of the region name and UUID of the object for example. But if there is no way to query it and it changes all the time, how is this supposed to be useful? --[[User:Maike Short|Maike Short]] 12:53, 17 October 2008 (PDT) | I am sorry but I fail how this can make any sense without a stable URL. The url could consist of the region name and UUID of the object for example. But if there is no way to query it and it changes all the time, how is this supposed to be useful? --[[User:Maike Short|Maike Short]] 12:53, 17 October 2008 (PDT) | ||
== Wrong Content type == | |||
The article says | |||
: "The content type of the returned data is always 'text/plain; utf-8'" | |||
but [[:Image:Lsl_http_server.JPG]] shows xml. So the content type text/plain is wrong and must be text/xml or application/xml. It may be better to allow returning of text without that xml structure, through as it is easier to parse and can be extended to html without breaking compatibility by allowing the setting of text/html as content type. --[[User:Maike Short|Maike Short]] 02:51, 18 October 2008 (PDT) | |||
Revision as of 01:51, 18 October 2008
Stable URL
I am sorry but I fail how this can make any sense without a stable URL. The url could consist of the region name and UUID of the object for example. But if there is no way to query it and it changes all the time, how is this supposed to be useful? --Maike Short 12:53, 17 October 2008 (PDT)
Wrong Content type
The article says
- "The content type of the returned data is always 'text/plain; utf-8'"
but Image:Lsl_http_server.JPG shows xml. So the content type text/plain is wrong and must be text/xml or application/xml. It may be better to allow returning of text without that xml structure, through as it is easier to parse and can be extended to html without breaking compatibility by allowing the setting of text/html as content type. --Maike Short 02:51, 18 October 2008 (PDT)
