The "SimpleServlet" is an example showing how Autoplot can be used to produce graphics for clients via HTTP. Request parameters are sent to the servlet, indicating the data set URI or vap file to plot, and parameters such as plot size. Autoplot then produces a static image or PDF on the server side, and sends the result.
Typically this would be used to serve data from files on the server side to clients. Note that URIs need not be local files, but remote files will be cached locally on the server, potentially causing problems. Please understand the limitations of the server before deploying it for production use, and contact us (autoplot@groups.google.com) if you have questions.
The "ScriptServlet" allows Jython scripts to be sent and interpreted to produce graphics or to access Autoplot internals. Obviously this introduces security concerns, and access is limited by the "allowhosts" file found by default in /tmp/autoplotservlet. Also, scripts are logged in this location as well.
The "ScriptGUIServlet" demonstrates how a Jython script can be automatically converted to a web application, automatically creating a form and showing the result.
The "URI_Templates" allows how an Autoplot script can be used to implement a service, here demonstrating Autoplot's implementation of the URI templates (https://github.com/hapi-server/uri-templates/wiki/Specification).
The "CdawebVapServlet" creates v1.08 vap files.
"ServletInfo" shows information about the servlet for debugging.
"Completions" shows how to get completions, which could be used to create a more interactive client.
"Thin" shows how Autoplot is used to implement a thin-client that is usable on phones.
The source for all of these is found at SourceForge.
Note: These are provided as examples and there is no guarantee of security. Data providers interested in using this software on their servers must do so at their own risk.
simple.jsp: web form for sending requests to the SimpleServlet.
script.jsp: web form for sending scripts to the ScriptServlet.
unaggregate.jsp: demo for URI templates, and also how servlets can be made from scripts.
thin: a more fully-developed thin-client app.