Actually, there is a bit of magic.
The DUCC CLI is not "REST"ful. It uses HTTP to send serialized java
objects. The serialization mechanism is XSteam, which is a
character-based serializtion, but in the end, the receiver must be able
to un-xstream the payload into java objects. The CLI enriches the
submitted properties in various ways (I forget the details) and sends
this serialized object to the DUCC Orchestrator (or Service Manager, for
service-y things). One of the enriched properties in there is a
binary-serialized authentication blob, built using the java.security
package.
So if your intent is to try to do this through scripting or a browser
front-end, it's technically possible, but probably not practical.
Jim
On 11/30/15 6:11 AM, Lou DeGenaro wrote:
There is nothing magical about DUCC's CLI/API, though it is quite
convenient. If one wanted to send/receive HTTP directly to the appropriate
DUCC daemon one could. Fetch the DUCC's CLI package source code to
discover how it is done.
Lou.
On Sun, Nov 29, 2015 at 6:19 PM, Eddie Epstein <[email protected]> wrote:
On Sat, Nov 28, 2015 at 7:28 PM, Yi-Wen Liu <[email protected]> wrote:
Hi,
Yes I've looked at the document.
Sorry I am not sure I am understanding, so because of security identity
issue, it is not allowed to simply send http request to the ducc server
by
the user?
Yes, I believe this is correct.
Eddie
