This is the rfc2388-binary Reference Manual, generated automatically by Declt version 4.0 beta 2 "William Riker" on Mon Aug 15 05:46:38 2022 GMT+0.
Next: Modules, Previous: The rfc2388-binary Reference Manual, Up: The rfc2388-binary Reference Manual [Contents][Index]
The main system appears first, followed by any subsystem dependency.
Next: Files, Previous: Systems, Up: The rfc2388-binary Reference Manual [Contents][Index]
Modules are listed depth-first from the system components tree.
rfc2388-binary (system).
Next: Packages, Previous: Modules, Up: The rfc2388-binary Reference Manual [Contents][Index]
Files are sorted by type and then listed depth-first from the systems components trees.
Next: rfc2388-binary/source/packages.lisp, Previous: Lisp, Up: Lisp [Contents][Index]
rfc2388-binary (system).
Next: rfc2388-binary/source/utils.lisp, Previous: rfc2388-binary/rfc2388-binary.asd, Up: Lisp [Contents][Index]
source (module).
Next: rfc2388-binary/source/api.lisp, Previous: rfc2388-binary/source/packages.lisp, Up: Lisp [Contents][Index]
packages.lisp (file).
source (module).
Next: rfc2388-binary/source/parsing.lisp, Previous: rfc2388-binary/source/utils.lisp, Up: Lisp [Contents][Index]
source (module).
mime-header (class).
Previous: rfc2388-binary/source/api.lisp, Up: Lisp [Contents][Index]
source (module).
Next: Definitions, Previous: Files, Up: The rfc2388-binary Reference Manual [Contents][Index]
Packages are listed by definition order.
common-lisp.
Next: Indexes, Previous: Packages, Up: The rfc2388-binary Reference Manual [Contents][Index]
Definitions are sorted by export status, category, package, and then by lexicographic order.
Next: Internals, Previous: Definitions, Up: Definitions [Contents][Index]
Next: Generic functions, Previous: Public Interface, Up: Public Interface [Contents][Index]
Returns the value in header-value-string and any associated attributes.
Parses MIME entities, returning them as a list.
Each element in the list is of form: (body headers), where BODY is the
contents of MIME part, and HEADERS are all headers for that part.
BOUNDARY is a string used to separate MIME entities.
This is the convenience interface to READ-MIME, all data is read
into memory or a file and we assume that every byte in the data
corresponds to exactly one character.
The SOURCE and BOUNDARY arguments are passed unchanged to READ-MIME. See READ-MIME’s documentation for details.
Next: Classes, Previous: Ordinary functions, Up: Public Interface [Contents][Index]
Returns the mime-header object for the header named HEADER-NAME (a string).
Returns the value of the attribute named NAME in the header HEADER.
automatically generated reader method
automatically generated writer method
automatically generated reader method
automatically generated writer method
automatically generated reader method
automatically generated writer method
Parses the MIME entites in SOURCE.
SOURCE is either a vector of (unsigned-byte 8) or a stream whose
element-type is (unsigned-byte 8). BOUNDARY is either a string of
US-ASCII encodeable characters or a byte vector. CALLBACK is a
function which will be passed one argument, a MIME-PART
containing the headers of the mime part and must return the following
values:
- a byte-handler function. This is a one argument function which
will be passed every byte in the mime part’s content.
- a termination function. This is a function without arguments
and will be called when the operation finishes without errors.
It must return whatever is to be returned from read-mime.
- an optional abort function. This is a function without arguments and will be called when the operation is aborted due to an error.
READ-MIME consumes bytes from SOURCE and returns a list of the
whatever the various termination functions returned.
Example:
(read-mime #<a binary stream> "123"
(lambda (mime-part)
(values (lambda (byte) (collect-byte-somewhere byte))
(lambda () mime-part))))
This call would return a list of mime-part objects passing each
byte to collect-byte-somewhere.
You may also want to look at UCW for a real-world example.
Previous: Generic functions, Up: Public Interface [Contents][Index]
Previous: Public Interface, Up: Definitions [Contents][Index]
When T we compile the code with some logging statements built in.
Next: Ordinary functions, Previous: Special variables, Up: Internals [Contents][Index]
Assuming BYTE is an ASCII coded character retun the corresponding character.
In short: is it a space or a tab?
Returns an alist of the keys and values in KEY-VALUE-STRING.
KEY-VALUE-STRING is of the form: (w+="w+";)*
Reads the next header from STREAM. Returns, as the first
value, T if a header was found and NIL otherwise. When a header
is found two more values are returned: the header name (a
string) and the header value (also a string). Headers are
assumed to be encoded in 7bit ASCII.
The returned strings may actually be displaced arrays.
Reads from STREAM up to the next boundary. For every byte of
data in stream we call DATA-HANDLER passing it the byte. Returns
T if there’s more data to be read, NIL otherwise.
The ASSUME-FIRST-BOUNDARY parameter should T if we’re reading the first part of a MIME message, where there is no leading CR LF sequence.
Previous: Definitions, Up: The rfc2388-binary Reference Manual [Contents][Index]
| Jump to: | (
A C D F G H L M P R |
|---|
| Jump to: | (
A C D F G H L M P R |
|---|
Next: Data types, Previous: Functions, Up: Indexes [Contents][Index]
| Jump to: | *
A C H N S V |
|---|
| Jump to: | *
A C H N S V |
|---|
| Jump to: | A C F M P R S U |
|---|
| Jump to: | A C F M P R S U |
|---|