View in context in the libbitcoin Slack #general mirror.
web service is fully operational. This is the admin console for the server. The explore service is a RESTful service for chain queries, and the HTML accept type will be the block explorer that @Rowan Voskuil is currently working on. That will use explore for HTML initial page loads (based on accept header) and the websocket JSON service for background content loading. He's currently mocking the websocket interface on third party public data services. I'll soon enable the HTML common page response on explore , for all requests. By restricting the HTML block explorer to fixed content responses the security guarantees become much easier. The JSON explorer requests, and websocket (JSON) requests, are limited to store query.
So with these three endpoints we get an admin console, which can be isolated, a RESTful block explorer on HTML and JSON, and dynamic JSON content, for both the explorer and admin console via WebSockets. We'll be able to drop in TLS over all endpoints as well.