Struct dazeus::DaZeus

pub struct DaZeus<'a, T> { /* fields omitted */ }

The base DaZeus struct.

See the crate documentation for a more detailed instruction on how to get started with these DaZeus bindings.

Methods

impl<'a, T> DaZeus<'a, T> where
    T: Read + Write, 

fn new(conn: T) -> DaZeus<'a, T>

Create a new instance of DaZeus from the given connection.

fn listen(&self) -> Result<(), Error>

Loop wait for messages to receive in a blocking way.

fn subscribe<F>(
    &mut self,
    event: EventType,
    callback: F
) -> (ListenerHandle, Response) where
    F: FnMut(Event, &DaZeusClient) + 'a, 

Subscribe to an event type and call the callback function every time such an event occurs.

fn subscribe_command<F>(
    &mut self,
    command: &str,
    callback: F
) -> (ListenerHandle, Response) where
    F: FnMut(Event, &DaZeusClient) + 'a, 

Subscribe to a command and call the callback function every time such a command occurs.

Trait Implementations

impl<'a, T> DaZeusClient<'a> for DaZeus<'a, T> where
    T: Read + Write, 

fn try_send(&self, request: Request) -> Result<Response, Error>

Try to send a request to DaZeus

fn send(&self, request: Request) -> Response

Send a request to DaZeus and retrieve a Future in which the response will be contained.

fn unsubscribe(&mut self, handle: ListenerHandle) -> Response

Unsubscribe a listener for some event.

fn unsubscribe_all(&mut self, event: EventType) -> Response

Remove all subscriptions for a specific event type.

fn has_any_subscription(&self, event: EventType) -> bool

Check if there is any active listener for the given event type.

fn networks(&self) -> Response

Retrieve the networks the bot is connected to.

fn channels(&self, network: &str) -> Response

Retrieve the channels the bot is in for a given network.

fn message(&self, network: &str, channel: &str, message: &str) -> Response

Send a message to a specific channel using the PRIVMSG method.

fn notice(&self, network: &str, channel: &str, message: &str) -> Response

Send a CTCP NOTICE to a specific channel.

fn ctcp(&self, network: &str, channel: &str, message: &str) -> Response

Send a CTCP REQUEST to a specific channel.

fn ctcp_reply(&self, network: &str, channel: &str, message: &str) -> Response

Send a CTCP REPLY to a specific channel.

fn action(&self, network: &str, channel: &str, message: &str) -> Response

Send a CTCP ACTION to a specific channel

fn send_names(&self, network: &str, channel: &str) -> Response

Send a request for the list of nicks in a channel.

Note that the response will not contain the names data, instead listen for a names event. The Response will only indicate whether or not the request has been submitted successfully. The server may respond with an EventType::Names event any time after this request has been submitted.

fn send_whois(&self, network: &str, nick: &str) -> Response

Send a request for a whois of a specific nick on some network.

Note that the response will not contain the whois data, instead listen for a whois event. The Response will only indicate whether or not the request has been submitted successfully. The server may respond with an EventType::Whois event any time after this request has been submitted.

fn join(&self, network: &str, channel: &str) -> Response

Try to join a channel on some network.

fn part(&self, network: &str, channel: &str) -> Response

Try to leave a channel on some network.

fn nick(&self, network: &str) -> Option<String>

Retrieve the nickname of the bot on the given network.

fn handshake(&self, name: &str, version: &str, config: Option<&str>) -> Response

Send a handshake to the DaZeus core.

fn get_config(&self, name: &str, group: ConfigGroup) -> Response

Retrieve a config value from the DaZeus config.

fn get_highlight_char(&self) -> Option<String>

Retrieve the character that is used by the bot for highlighting.

fn get_property(&self, name: &str, scope: Scope) -> Response

Retrieve a property stored in the bot database.

fn set_property(&self, name: &str, value: &str, scope: Scope) -> Response

Set a property to be stored in the bot database.

fn unset_property(&self, name: &str, scope: Scope) -> Response

Remove a property stored in the bot database.

fn get_property_keys(&self, prefix: &str, scope: Scope) -> Response

Retrieve a list of keys starting with the common prefix with the given scope.

fn set_permission(
    &self,
    permission: &str,
    allow: bool,
    scope: Scope
) -> Response

Set a permission to either allow or deny for a specific scope.

fn has_permission(
    &self,
    permission: &str,
    default: bool,
    scope: Scope
) -> Response

Retrieve whether for some scope the given permission was set.

Will return the default if it was not.

fn unset_permission(&self, permission: &str, scope: Scope) -> Response

Remove a set permission from the bot.

fn whois(&mut self, network: &str, nick: &str) -> Event

Send a whois request and wait for an event that answers this request (blocking).

Note that the IRC server may not respond to the whois request (if it has been configured this way), in which case this request will block forever.

fn names(&mut self, network: &str, channel: &str) -> Event

Send a names request and wait for an event that answers this request (blocking).

Note that the IRC server may not respond to the names request (if it has been configured this way), in which case this request will block forever.

fn reply(&self, event: &Event, message: &str, highlight: bool) -> Response

Send a reply in response to some event.

Note that not all types of events can be responded to. Mostly message type events concerning some IRC user can be responded to. Join events can also be responded to.

fn reply_with_notice(&self, event: &Event, message: &str) -> Response

Send a reply (as a notice) in response to some event.

Note that not all types of events can be responded to. Mostly message type events concerning some IRC user can be responded to. Join events can also be responded to.

fn reply_with_action(&self, event: &Event, message: &str) -> Response

Send a reply (as a ctcp action) in response to some event.

Note that not all types of events can be responded to. Mostly message type events concerning some IRC user can be responded to. Join events can also be responded to.