Login or Register to Ask a Question and Join Our Community


Software Releases - RSS News

gPodder 0.14.1 (Default branch)

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News gPodder 0.14.1 (Default branch)
# 1  
Old 02-02-2009
gPodder 0.14.1 (Default branch)
Image gPodder is a Podcast receiver/catcher written in Python and pyGTK. It manages podcast feeds for you, and automatically downloads all podcasts from as many feeds as you like. If you are interested in Podcast feeds, simply put the feed URLs into gPodder and it will download all episodes for you automatically. If there is a new episode, it will get it for you. It supports download resume, if the server supports it. License: GNU General Public License (GPL) Changes:
The Spanish, Russian, Finnish, Swedish, and French translations have been updated. Some bugs in the user interface have also been fixed. This release is recommended for all users of previous versions. Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question

LEARN ABOUT DEBIAN

zmq_ipc

ZMQ_IPC(7)							    0MQ Manual								ZMQ_IPC(7)

NAME

       zmq_ipc - 0MQ local inter-process communication transport

SYNOPSIS

       The inter-process transport passes messages between local processes using a system-dependent IPC mechanism.

	   Note
	   The inter-process transport is currently only implemented on operating systems that provide UNIX domain sockets.

ADDRESSING

       A 0MQ address string consists of two parts as follows: transport://endpoint. The transport part specifies the underlying transport protocol
       to use, and for the inter-process transport shall be set to ipc. The meaning of the endpoint part for the inter-process transport is
       defined below.

   Assigning a local address to a socket
       When assigning a local address to a socket using zmq_bind() with the ipc transport, the endpoint shall be interpreted as an arbitrary
       string identifying the pathname to create. The pathname must be unique within the operating system namespace used by the ipc
       implementation, and must fulfill any restrictions placed by the operating system on the format and length of a pathname.

   Connecting a socket
       When connecting a socket to a peer address using zmq_connect() with the ipc transport, the endpoint shall be interpreted as an arbitrary
       string identifying the pathname to connect to. The pathname must have been previously created within the operating system namespace by
       assigning it to a socket with zmq_bind().

WIRE FORMAT

       Not applicable.

EXAMPLES

       Assigning a local address to a socket.

	   /* Assign the pathname "/tmp/feeds/0" */
	   rc = zmq_bind(socket, "ipc:///tmp/feeds/0");
	   assert (rc == 0);

       Connecting a socket.

	   /* Connect to the pathname "/tmp/feeds/0" */
	   rc = zmq_connect(socket, "ipc:///tmp/feeds/0");
	   assert (rc == 0);

SEE ALSO

       zmq_bind(3) zmq_connect(3) zmq_inproc(7) zmq_tcp(7) zmq_pgm(7) zmq(7)

AUTHORS

       This manual page was written by the 0MQ community.

0MQ 2.2.0							    04/04/2012								ZMQ_IPC(7)