| … | |
… | |
| 127 | and no read request is in the queue (unlike read queue callbacks, this |
127 | and no read request is in the queue (unlike read queue callbacks, this |
| 128 | callback will only be called when at least one octet of data is in the |
128 | callback will only be called when at least one octet of data is in the |
| 129 | read buffer). |
129 | read buffer). |
| 130 | |
130 | |
| 131 | To access (and remove data from) the read buffer, use the C<< ->rbuf >> |
131 | To access (and remove data from) the read buffer, use the C<< ->rbuf >> |
| 132 | method or access the C<$handle->{rbuf}> member directly. |
132 | method or access the C<$handle->{rbuf}> member directly. Note that you |
|
|
133 | must not enlarge or modify the read buffer, you can only remove data at |
|
|
134 | the beginning from it. |
| 133 | |
135 | |
| 134 | When an EOF condition is detected then AnyEvent::Handle will first try to |
136 | When an EOF condition is detected then AnyEvent::Handle will first try to |
| 135 | feed all the remaining data to the queued callbacks and C<on_read> before |
137 | feed all the remaining data to the queued callbacks and C<on_read> before |
| 136 | calling the C<on_eof> callback. If no progress can be made, then a fatal |
138 | calling the C<on_eof> callback. If no progress can be made, then a fatal |
| 137 | error will be raised (with C<$!> set to C<EPIPE>). |
139 | error will be raised (with C<$!> set to C<EPIPE>). |
| … | |
… | |
| 767 | ) { |
769 | ) { |
| 768 | $self->_error (&Errno::ENOSPC, 1), return; |
770 | $self->_error (&Errno::ENOSPC, 1), return; |
| 769 | } |
771 | } |
| 770 | |
772 | |
| 771 | while () { |
773 | while () { |
|
|
774 | # we need to use a separate tls read buffer, as we must not receive data while |
|
|
775 | # we are draining the buffer, and this can only happen with TLS. |
| 772 | $self->{rbuf} .= delete $self->{_tls_rbuf} if exists $self->{_tls_rbuf}; |
776 | $self->{rbuf} .= delete $self->{_tls_rbuf} if exists $self->{_tls_rbuf}; |
| 773 | |
777 | |
| 774 | my $len = length $self->{rbuf}; |
778 | my $len = length $self->{rbuf}; |
| 775 | |
779 | |
| 776 | if (my $cb = shift @{ $self->{_queue} }) { |
780 | if (my $cb = shift @{ $self->{_queue} }) { |
| … | |
… | |
| 839 | |
843 | |
| 840 | =item $handle->rbuf |
844 | =item $handle->rbuf |
| 841 | |
845 | |
| 842 | Returns the read buffer (as a modifiable lvalue). |
846 | Returns the read buffer (as a modifiable lvalue). |
| 843 | |
847 | |
| 844 | You can access the read buffer directly as the C<< ->{rbuf} >> member, if |
848 | You can access the read buffer directly as the C<< ->{rbuf} >> |
| 845 | you want. |
849 | member, if you want. However, the only operation allowed on the |
|
|
850 | read buffer (apart from looking at it) is removing data from its |
|
|
851 | beginning. Otherwise modifying or appending to it is not allowed and will |
|
|
852 | lead to hard-to-track-down bugs. |
| 846 | |
853 | |
| 847 | NOTE: The read buffer should only be used or modified if the C<on_read>, |
854 | NOTE: The read buffer should only be used or modified if the C<on_read>, |
| 848 | C<push_read> or C<unshift_read> methods are used. The other read methods |
855 | C<push_read> or C<unshift_read> methods are used. The other read methods |
| 849 | automatically manage the read buffer. |
856 | automatically manage the read buffer. |
| 850 | |
857 | |
