The Perl Toolchain Summit needs more sponsors. If your company depends on Perl, please support this very important event.

NAME

Padre::Swarm::Manual - Guide to Swarm

DESCRIPTION

PROTOCOL

The Swarm protocol at present is very ad-hoc and subject to change. Message delivery is NEVER guaranteed, there are no unique message IDs - nor any acknowledgement that a sent message has arrived.. anywhere.

A swarm message should always have a type , service , from, title and body. It may also have a to , resource.

type=disco

Discovery message requesting information from other swarm agents. Generally a discovery will trigger a promote response from a service, if that service chooses to advertise itself.

type=promote

Advertisment of a service provided by an agent.

type=chat

A public chat message. Expected to contain a body.

type=runme

Request for remote execution! Receivers brave enough are expected to run message body with string eval. :)

type=openme

Suggestion to open an editor document containing message body