If --mgtPort is the same as the main port the server is running, or it's
zero, then the admin and server info functions are under /$/ on the one
port.
Andy
On 08/11/13 15:56, Andy Seaborne wrote:
On 08/11/13 14:08, Ian Dickinson wrote:
On Fri, Nov 8, 2013 at 11:48 AM, Andy Seaborne
On 08/11/13 14:08, Ian Dickinson wrote:
On Fri, Nov 8, 2013 at 11:48 AM, Andy Seaborne wrote:
There are three categories of operations:
1/ interacting with datasets
2/ inspection of the server (read-only, meta requests)
3/ administation/change of the server
Just to note: in order to bootstrap
On Fri, Nov 8, 2013 at 11:48 AM, Andy Seaborne wrote:
> There are three categories of operations:
>
> 1/ interacting with datasets
> 2/ inspection of the server (read-only, meta requests)
> 3/ administation/change of the server
Just to note: in order to bootstrap #1, in the new UI I need to be
abl
On Fri, Nov 8, 2013 at 11:42 AM, Andy Seaborne wrote:
> What is there is legacy and getting something that worked in the olden days.
> The world has moved on (mostly). More to the point, JS toolkits help deal
> with the differences in browsers.
>
> At very worst, we simply leave the old stuff aro
On 06/11/13 17:26, Ian Dickinson wrote:
...
OK, first issue: currently, we have the notion that the management
capability should be available as a separate endpoint, serving JSON.
This is so that both the new UI, and also command-line scripts and
build automation tools can drive the Fuseki manage
On 07/11/13 10:47, Ian Dickinson wrote:
Next issue: currently, the Fuseki control-panel allows the user to
select one of the current datasets by having the server dynamically
construct an HTML page with the id's of the current datasets built-in
to an options element. Do we want to replace this fu
Next issue: currently, the Fuseki control-panel allows the user to
select one of the current datasets by having the server dynamically
construct an HTML page with the id's of the current datasets built-in
to an options element. Do we want to replace this functionality with
the client-side Javascrip
I'm starting this thread so that Andy and I can discuss design
questions on the new Fuseki UI. Contributions and comments from
everyone welcome! We'll try to record actual design decisions on
Jena-420 [1].
OK, first issue: currently, we have the notion that the management
capability should be avai
