Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

eiskaltdcpp-daemon(1) [debian man page]

eiskaltdcpp-daemon(1)					      General Commands Manual					     eiskaltdcpp-daemon(1)

eiskaltdcpp-daemon - simple daemon controllable via XMLRPC or JSONRPC SYNOPSIS
eiskaltdcpp-daemon -d eiskaltdcpp-daemon <Key> DESCRIPTION
EiskaltDC++ is a cross-platform program that uses the Direct Connect and ADC protocol. It is compatible with other DC clients, such as the original DC from Neomodus, DC++ and derivatives. EiskaltDC++ also interoperates with all common DC hub software. COMMAND LINE OPTIONS
A summary of options is included below. -d,--daemon" Run program as daemon -v,--verbose" Verbose mode -D,--debug" Debug mode -P <port>,--port=<port>" Set port for XMLRPC or JSONRPC (default: 3121) -L <ip>,--ip=<ip>" Set IP address for XMLRPC or JSONRPC (default: -p file,--pidfile=<file>" Write daemon process ID to <file> -c dir,--confdir=<dir>" Store config in <dir> -l <dir>,--localdir=<dir>" Store local data (cache, temp files) in <dir> (defaults is equal confdir) -S <file>,--rpclog=<file>" Write xmlrpc log to <file> (default: /tmp/eiskaltdcpp-daemon.xmlrpc.log) -U <uripath>,--uripath=<uripath>" Set UriPath for xmlrpc abyss server to <uripath> (default: /eiskaltdcpp) -h, --help Display help and exit -V, --version Show version information and exit FILES
~/.config/eiskaltdc++/ or $XDG_CONFIG_HOME/eiskaltdc++/ Directory with user configuration files DOCUMENTATION
Detail documentation about available XMLRPC and JSONRPC methods can be found in our wiki: AUTHOR
This program was written by EiskaltDC++ developers team (see file AUTHORS). EiskaltDC++ homepage: BUG REPORTS
If you find a bug in EiskaltDC++ please report it here: This manual page was written by Boris Pek <> for the Debian project (and may be used by others). 19 Feb 2012 eiskaltdcpp-daemon(1)

Check Out this Related Man Page

XMLRPC::Transport::HTTP(3)				User Contributed Perl Documentation				XMLRPC::Transport::HTTP(3)

XMLRPC::Transport::HTTP - Server/Client side HTTP support for XMLRPC::Lite SYNOPSIS
Client use XMLRPC::Lite proxy => 'http://localhost/', # proxy => 'http://localhost/cgi-bin/xmlrpc.cgi', # local CGI server # proxy => 'http://localhost/', # local daemon server # proxy => 'http://login:password@localhost/cgi-bin/xmlrpc.cgi', # local CGI server with authentication ; print getStateName(1); CGI server use XMLRPC::Transport::HTTP; my $server = XMLRPC::Transport::HTTP::CGI -> dispatch_to('methodName') -> handle ; Daemon server use XMLRPC::Transport::HTTP; my $daemon = XMLRPC::Transport::HTTP::Daemon -> new (LocalPort => 80) -> dispatch_to('methodName') ; print "Contact to XMLRPC server at ", $daemon->url, " "; $daemon->handle; DESCRIPTION
This class encapsulates all HTTP related logic for a XMLRPC server, independent of what web server it's attached to. If you want to use this class you should follow simple guideline mentioned above. PROXY SETTINGS You can use any proxy setting you use with LWP::UserAgent modules: XMLRPC::Lite->proxy('http://endpoint.server/', proxy => ['http' => 'http://my.proxy.server']); or $xmlrpc->transport->proxy('http' => 'http://my.proxy.server'); should specify proxy server for you. And if you use "HTTP_proxy_user" and "HTTP_proxy_pass" for proxy authorization SOAP::Lite should know how to handle it properly. COOKIE-BASED AUTHENTICATION use HTTP::Cookies; my $cookies = HTTP::Cookies->new(ignore_discard => 1); # you may also add 'file' if you want to keep them between sessions my $xmlrpc = XMLRPC::Lite->proxy('http://localhost/'); $xmlrpc->transport->cookie_jar($cookies); Cookies will be taken from response and provided for request. You may always add another cookie (or extract what you need after response) with HTTP::Cookies interface. You may also do it in one line: $xmlrpc->proxy('http://localhost/', cookie_jar => HTTP::Cookies->new(ignore_discard => 1)); COMPRESSION XMLRPC::Lite provides you option for enabling compression on wire (for HTTP transport only). Both server and client should support this capability, but this logic should be absolutely transparent for your application. Server will respond with encoded message only if client can accept it (client sends Accept-Encoding with 'deflate' or '*' values) and client has fallback logic, so if server doesn't understand specified encoding (Content-Encoding: deflate) and returns proper error code (415 NOT ACCEPTABLE) client will repeat the same request not encoded and will store this server in per-session cache, so all other requests will go there without encoding. Having options on client and server side that let you specify threshold for compression you can safely enable this feature on both client and server side. Compression will be enabled on client side IF: threshold is specified AND size of current message is bigger than threshold AND module Compress::Zlib is available. Client will send header 'Accept-Encoding' with value 'deflate' if threshold is specified AND module Compress::Zlib is available. Server will accept compressed message if module Compress::Zlib is available, and will respond with compressed message ONLY IF: threshold is specified AND size of current message is bigger than threshold AND module Compress::Zlib is available AND header 'Accept-Encoding' is presented in request. DEPENDENCIES
Crypt::SSLeay for HTTPS/SSL HTTP::Daemon for XMLRPC::Transport::HTTP::Daemon Apache, Apache::Constants for XMLRPC::Transport::HTTP::Apache SEE ALSO
See ::CGI, ::Daemon and ::Apache for implementation details. See examples/XMLRPC/* for examples. COPYRIGHT
Copyright (C) 2000-2001 Paul Kulchenko. All rights reserved. This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. AUTHOR
Paul Kulchenko ( perl v5.12.1 2010-03-18 XMLRPC::Transport::HTTP(3)
Man Page

Featured Tech Videos