Author image Tom Molesworth
and 1 contributors

data

Returns a Future which will resolve when the given item is available. Suitable for smaller data strucures such as the envelope. Not recommended for the full body of a message, unless you really want to load the entire message data into memory.

stream

This is what you would normally use for a message, although at the moment you can't, so don't.

my $msg = $imap->fetch(message => 123); $msg->data('envelope')->on_done(sub { my $envelope = shift; say "Date: " . $envelope->date; say "From: " . join ',', $envelope->from; say "To: " . join ',', $envelope->to; say "CC: " . join ',', $envelope->cc; say "BCC: " . join ',', $envelope->bcc; });

Implementation:

The untagged FETCH response causes instantiation of this class. We pass the fetch line as the initial buffer, set up the parser and run the first parse attempt.

If we already have enough data to parse the FETCH response, then we relinquish control back to the client.

If there's a {123} string literal, then we need to stream that amount of data: we request a new sink, primed with the data we have so far, with the byte count ({123} value) as the limit, and allow it to pass us events until completion.

In streaming mode, we'll pass those to event listeners. Otherwise, we'll store this data internally to the appropriate key.

then switch back to line mode.

INHERITED METHODS

Mixin::Event::Dispatch

add_handler_for_event, clear_event_handlers, event_handlers, invoke_event, subscribe_to_event, unsubscribe_from_event