VisKo currently requires that all visualization operators be exposed as WSDL services. We would like to move to an infrastructure that is more flexible and can interfaced with operators exposed at servlets (via WADL) or even local API code (e.g., jars, dll's, and .so).
VisKo currently requires that all visualization operators be exposed as WSDL services. We would like to move to an infrastructure that is more flexible and can interfaced with operators exposed at servlets (via WADL) or even local API code (e.g., jars, dll's, and .so).