#188: Remove CLI and add an alternative. (Invalid)

Back to ticket list | See last change
Aug 20 2007 * 01:40
Reported by: Release:
Priority: Normal Milestone: 2.0
Component: Assigned to: 
*****************************************************
 This ticket is part of a global brainstorm, so it's 
 not a real ticket. It's here for comments. 
 This is basically an item of the TODO list for 2.0
*****************************************************

This is one of the most important things… We should remove the CLI and its locks… and finally add (and find) one (or more) alternatives to the CLI. My proposal is XMLRPC.

Changelog:

Modified by Aug 20 2007 * 07:30

I agree on your proposal. XML-RPC looks like the way to go.

Modified by Sep 11 2007 * 09:08

Whatever you wanna use the important is to give all the debugging stuffs back to the developer.

Also all the LOG function of the whole source have to be checked there are messages that are quite unusefull and just add junk to the logs.

I’ll be fine if i can have debug and ogi debug event also for the manager interface.

Modified by Sep 16 2007 * 10:54

XMLRPC has one big disadvantage. The specs require that the transport be HTTP with POST method. And we don’t want a HTTP-server in CW =)

We could ignore that part and put it on some other transport. I’d recommend BEEP, since then we don’t have to implement our own auth scheme and it has TLS support built in. And there is a SOAP-over-BEEP RFC that we probably could reuse for XMLRPC

THen again we could just use SOAP-RPC over BEEP. Although soap is the king of bloat, we don’t have to care about anything more than the most basic RPC functionality.

Modified by Sep 16 2007 * 11:03

One more thing,

We need to have a protocol that allows bi-directional calls.

This is needed because both the CLI and CW can be an initiator of something. The CLI initiates an RPC-call when it wants CW to do something, and CW can initiate a RPC-call when it wants to send an event, logging, etc to the CLI.

Modified by Oct 05 2007 * 06:33

REST (http://en.wikipedia.org/wiki/Representational_State_Transfer) has gained quite a lot of momentum for HTTP based services. Is it usable in our environment?

Modified by Oct 05 2007 * 06:36

We should replace the Manager Interface with something like this as well.

Modified by Oct 26 2007 * 05:18

Please see Connexion project as management framework. It can be example for different interfaces (CLI, XML-RPC, HTTP) for same management operations.

http://www.radlinux.org/connexion/wiki http://www.radlinux.org/docs/static/en/ http://www.radlinux.org/download/

Modified by Nov 17 2008 * 04:18

I’m sorry but what the disadvantages of CLI, which will costs developers efforts?

At the time CLI do almost everything administrator need from anyplace.

As for me there is a lot of things which developers should focus on.

Modified by Jun 05 2010 * 15:21
  • Status: changed from Open to Invalid