Re: [RFC} New Commanline Syntax for Telnet interface

On Fri, Aug 30, 2002, Jean-Paul Saman wrote:
> Start
> The start command has new options: --rtp.
Whoo :)

> Resume
> The resume command will only need the channel
> resume <channel>
> suspend <channel>
> stop <channel>

I think this is a great idea, since we don't care about what is
streamed, but who receives the scream. 

However, I hope this change of syntax will not be an big problem for
people who use scripts that send telnet commands, such as the Bill
Eldridge http interface, of the Perl/Tk manager.

> program <name> <input> <filename> <type> [--add] [--delete]

> channel <name> <channeltype=[local|network]> 
> <dest_host=[FQDN|ipaddress]> <dest_port> <type 
> (unicast|multicast|broadcast)> [domain (inet4|inet6)] [ttl] [intf] 
> [--add] [--delete]

This actual syn tax does not fit me (sorry to tell you only now :),
because this imply to type all the parameters (or random ones) when
deleting a channel or a program :

> channel bogey network bogey.humprey.com 1234 unicast domain inet4 --add

To delete it, one would have to type :
channel bogey network bogey.humprey.com 1234 unicast --delete

and it would be better to have : 
channel bogey --delete

which is not possible, since <name> <channeltype> ... are compulsory.

So we could make <name> <channeltype> (...) become optionnal, but we
would not get the benefit of arguments checking.

So I propose to split up in 2 commands :

channeladd <name> <channeltype=[local|network]> 
 <dest_host=[FQDN|ipaddress]> <dest_port> <type 
 (unicast|multicast|broadcast)> [domain (inet4|inet6)] [ttl] [intf] 

and 

channeldelete <name> ,

and the same for input and program.

Do you think it is a better idea ?

Regards,

-- 
Tristan
-- 
This is the vls-devel mailing-list, see http://www.videolan.org/vls-devel/
To unsubscribe, please read http://www.videolan.org/lists.html
If you are in trouble, please contact <[email protected]>