Protocol-IMAP

 view release on metacpan or  search on metacpan

lib/Protocol/IMAP/Fetch.pm  view on Meta::CPAN

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.

lib/Protocol/IMAP/Fetch.pod  view on Meta::CPAN

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.

=head1 INHERITED METHODS

=over 4

=item L<Mixin::Event::Dispatch>



( run in 0.239 second using v1.01-cache-2.11-cpan-4d50c553e7e )