POE::Component::Client::MPD - full-blown poe-aware mpd client library


version 2.001


    use POE qw{ Component::Client::MPD };
    POE::Component::Client::MPD->spawn( {
        host           => 'localhost',
        port           => 6600,
        password       => 's3kr3t',  # mpd password
        alias          => 'mpd',     # poe alias
        status_msgs_to => 'myapp',   # session to send status info to
    } );

    # ... later on ...
    $_[KERNEL]->post( mpd => 'next' );


POCOCM gives a clear message-passing interface (sitting on top of POE) for talking to and controlling MPD (Music Player Daemon) servers. A connection to the MPD server is established as soon as a new POCOCM object is created.

Commands are then sent to the server as messages are passed.



The hostname where MPD is running. Defaults to environment var MPD_HOST, then to 'localhost'. Note that MPD_HOST can be of the form password@host:port (each of password@ or :port can be omitted).


The port that MPD server listens to. Defaults to environment var MPD_PORT, then to parsed MPD_HOST (cf above), then to 6600.


The password to access special MPD functions. Defaults to environment var MPD_PASSWORD, then to parsed MPD_HOST (cf above), then to empty string.


A string to alias the newly created POE session. Defaults to mpd.


A session (name or id) to whom to send connection status to. Optional, although recommended. No default. When this is done, pococm will send *additional* events to the session, such as: mpd_connected when pococm is connected, mpd_disconnected when pococm is disconnected, etc. You thus need to register some handlers for those events.


my $id = POE::Component::Client::MPD->spawn( \%params );

This method will create a POE session responsible for communicating with mpd. It will return the poe id of the session newly created. You can tune it by passing some arguments as a hash reference. See the attributes for allowed values.


The goal of a POCOCM session is to drive a remote MPD server. This can be achieved by a lot of events. Due to their sheer number, they have been regrouped logically in modules.

However, note that to use those events, you need to send them to the POCOCM session that you created with spawn() (see above). Indeed, the logical split is only internal: you are to use the same peer.

For a list of public events that update and/or query MPD, see embedded pod in:

disconnect( )

Request the POCOCM to be shutdown. Leave mpd running. Generally sent when one wants to exit her program.


A POCOCM session will fire events, either to answer an incoming event, or to inform about some changes regarding the remote MPD server.

Answer events

For each incoming event received by the POCOCM session, it will fire back one of the following answers:

Auto-generated events

If you supplied the status_msgs_to attribute, the following events are fired to this peer by pococm:

  • mpd_connect_error( $reason )

    Called when pococm-conn could not connect to a mpd server. It can be either retriable, or fatal. Check $reason for more information.

  • mpd_connected( )

    Called when pococm-conn made sure we're talking to a mpd server.

  • mpd_disconnected( )

    Called when pococm-conn has been disconnected from mpd server.


You can find more information on the mpd project on its homepage at, or its wiki You may want to have a look at Audio::MPD, a non-POE aware module to access MPD.

You can look for information on this module at:


Jerome Quelin


This software is copyright (c) 2007 by Jerome Quelin.

This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.