poe::filter::httpchunk(3pm) [debian man page]

POE::Filter::HTTPChunk(3pm)				User Contributed Perl Documentation			       POE::Filter::HTTPChunk(3pm)

my $TEXT = qr/[^[:cntrl:]]/o; my $qdtext = qr/[^[:cntrl:]"]/o; #<any TEXT except <">> my $quoted_pair = qr/\[[:ascii:]]/o; my $quoted_string =
qr/"(?:$qdtext|$quoted_pair)"/o; my $separators = "[^()<>@,;:\"/[]?={} 	"; my $notoken = qr/(?:[[:cntrl:]$separators]/o;

       my $chunk_ext_name = $token; my $chunk_ext_val = qr/(?:$token|$quoted_string)/o;

       my $chunk_extension = qr/(?:;$chunk_ext_name(?:$chunk_ext_val)?)/o;

       sub put {
	 die "not implemented yet"; }

NAME

       POE::Filter::HTTPChunk - Non-blocking incremental HTTP chunk parser.

VERSION

       version 0.947

SYNOPSIS

	 # Not a complete program.
	 use POE::Filter::HTTPChunk;
	 use POE::Wheel::ReadWrite;
	 sub setup_io {
	   $_[HEAP]->{io_wheel} = POE::Wheel::ReadWrite->new(
	     Filter => POE::Filter::HTTPChunk->new(),
	     # See POE::Wheel::ReadWrite for other required parameters.
	   );
	 }

DESCRIPTION

       This filter parses HTTP chunks from a data stream.  It's used by POE::Component::Client::HTTP to do the bulk of the low-level HTTP parsing.

CONSTRUCTOR

   new
       "new" takes no parameters and returns a shiny new POE::Filter::HTTPChunk object ready to use.

METHODS

       POE::Filter::HTTPChunk supports the following methods.  Most of them adhere to the standard POE::Filter API.  The documentation for
       POE::Filter explains the API in more detail.

   get_one_start ARRAYREF
       Accept an arrayref containing zero or more raw data chunks.  They are added to the filter's input buffer.  The filter will attempt to parse
       that data when get_one() is called.

	 $filter_httpchunk->get_one_start(@stream_data);

   get_one
       Parse a single HTTP chunk from the filter's input buffer.  Data is entered into the buffer by the get_one_start() method.  Returns an
       arrayref containing zero or one parsed HTTP chunk.

	 $ret_arrayref = $filter_httpchunk->get_one();

   get_pending
       Returns an arrayref of stream data currently pending parsing.  It's used to seamlessly transfer unparsed data between an old and a new
       filter when a wheel's filter is changed.

	 $pending_arrayref = $filter_httpchunk->get_pending();

SEE ALSO

       POE::Filter, POE.

BUGS

       None are known at this time.

AUTHOR &; COPYRIGHTS
       POE::Filter::HTTPChunk is...

       o Copyright 2005-2006 Martijn van Beers

       o Copyright 2006 Rocco Caputo

       All rights are reserved.  POE::Filter::HTTPChunk is free software; you may redistribute it and/or modify it under the same terms as Perl
       itself.

CONTACT

       Rocco may be contacted by e-mail via <mailto:rcaputo@cpan.org>, and Martijn may be contacted by email via <mailto:martijn@cpan.org>.

       The preferred way to report bugs or requests is through RT though.  See http://rt.cpan.org/NoAuth/Bugs.html?Dist=POE-Component-Client-HTTP
       <http://rt.cpan.org/NoAuth/Bugs.html?Dist=POE-Component-Client-HTTP> or mail mailto:bug-POE-Component-Client-HTTP@rt.cpan.org <mailto:bug-
       POE-Component-Client-HTTP@rt.cpan.org>

       For questions, try the POE mailing list (poe@perl.org)

perl v5.14.2							    2012-06-03					       POE::Filter::HTTPChunk(3pm)

Check Out this Related Man Page

POE::Driver::SysRW(3pm) 				User Contributed Perl Documentation				   POE::Driver::SysRW(3pm)

NAME

       POE::Driver::SysRW - buffered, non-blocking I/O using sysread and syswrite

SYNOPSIS

       "SYNOPSIS" in POE::Driver illustrates how the interface works.  This module is merely one implementation.

DESCRIPTION

       This driver implements POE::Driver using sysread and syswrite.

PUBLIC METHODS

       POE::Driver::SysRW introduces some additional features not covered in the base interface.

   new [BlockSize => OCTETS]
       new() creates a new buffered I/O driver that uses sysread() to read data from a handle and syswrite() to flush data to that handle.  The
       constructor accepts one optional named parameter, "BlockSize", which indicates the maximum number of OCTETS that will be read at one time.

       "BlockSize" is 64 kilobytes (65536 octets) by default.  Higher values may improve performance in streaming applications, but the trade-off
       is a lower event granularity and increased resident memory usage.

       Lower "BlockSize" values reduce memory consumption somewhat with corresponding throughput penalties.

	 my $driver = POE::Driver::SysRW->new;

	 my $driver = POE::Driver::SysRW->new( BlockSize => $block_size );

       Drivers are commonly instantiated within POE::Wheel constructor calls:

	 $_[HEAP]{wheel} = POE::Wheel::ReadWrite->new(
	   InputHandle => *STDIN,
	   OutputHandle => *STDOUT,
	   Driver => POE::Driver::SysRW->new(),
	   Filter => POE::Filter::Line->new(),
	 );

       Applications almost always use POE::Driver::SysRW, so POE::Wheel objects almost always will create their own if no Driver is specified.

   All Other Methods
       POE::Driver::SysRW documents the abstract interface documented in POE::Driver.  Please see POE::Driver for more details about the following
       methods:

       flush
       get
       get_out_messages_buffered
       put

SEE ALSO

       POE::Driver, POE::Wheel.

       Also see the SEE ALSO section of POE, which contains a brief roadmap of POE's documentation.

AUTHORS &; COPYRIGHTS
       Please see POE for more information about authors and contributors.

perl v5.14.2							    2012-05-15						   POE::Driver::SysRW(3pm)

Linux and UNIX Man Pages

poe::filter::httpchunk(3pm) [debian man page]

Check Out this Related Man Page