File tree Expand file tree Collapse file tree 1 file changed +4
-5
lines changed Expand file tree Collapse file tree 1 file changed +4
-5
lines changed Original file line number Diff line number Diff line change 613613 \begin {itemize }
614614 \item \texttt {MSG\_ PEEK } \dots {} message it considered not read, next
615615 \texttt {recvfrom } will return it again
616- \item \texttt {MSG\_ OOB } \dots {} reads urgent (out-of-band)
617- data
616+ \item \texttt {MSG\_ OOB } \dots {} reads urgent (out-of-band) data
618617 \item \texttt {MSG\_ WAITALL } \dots {} waits for the buffer to fill up
619618 i.e. \emph {l{}en } bytes
620619 \end {itemize }
634633Depending on the application, using large buffer (based on lower network layer
635634constraints) might be the answer (at the cost of wasting memory).
636635\item \texttt {address\_ len } \emsl {must} be initialized with buffer size if
637- the address is not \texttt {NULL }. \texttt {NULL } address is used to express that
638- the caller is not interested in remote's address -- however that is usually
639- not the case when working with datagrams.
636+ the \texttt { address } is not \texttt {NULL }. \texttt {NULL } address is used to
637+ express that the caller is not interested in remote's address -- however that is
638+ usually not the case when working with datagrams.
640639\item Instead of using \texttt {recvfrom } it is possible to use
641640\texttt {recvmsg } which is more generic.
642641\item If \texttt {connect } was used then \texttt {recv } can be used instead of
You can’t perform that action at this time.
0 commit comments