| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
Doing this for code clarity, as its easier to see what the issues are
when you have all implementations in one file
|
| |
|
|
|
| |
Winsock2 requires calling a function to initialize the socket library.
This call can fail. Return an error code to the user if it does.
|
| |
|
|
|
|
|
|
|
|
| |
Publicly define the error codes returned from the various public API
functions. The error codes are defined in the amqp_status_enum and are
all negative in value to work with functions that return positive
values.
OS and SSL specific codes are no longer munged into the error code, as
it is unlikely for that information to be useful to library users.
|
| | |
|
| |
|
|
|
|
| |
Properly munge the error code from amqp_socket_init on Win32, previously
it was not munged correctly and an error code could be mistaken as a
sockfd
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change abstracts out the networking functions so that the
user can provide an SSL/TLS implementation.
Callback functions replace `writev()`, `send()`, and `recv()` (there
is also a callback for error reporting). The default interface remains
unchanged. If the user wants to create a SSL/TLS connection they first
negotiate the connection and then use the new function
`amqp_set_sockfd_full()` to provide the networking implementation for
their SSL/TLS library. The user may provide an optional pointer to data
that is passed through to the networking functions.
Signed-off-by: Michael Steinert <mike.steinert@gmail.com>
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
FormatMessage might be #defined to be FormatMessageW in case
UNICODE is #defined, expliciting calling the ascii version
of the function corrects this in all cases
|
|
|
1. Standardize on `win32` vs `windows/win32`
2. Move `msinttypes` into platform directory
Signed-off-by: Michael Steinert <mike.steinert@gmail.com>
|
