3f91647370
Move response deserialization into client
2022-03-22 16:47:12 +08:00
dd5fbc60ce
Simplify response tests with a helper
2022-03-22 16:47:12 +08:00
5dce8501d5
Let callers create CommandDocument directly
2022-03-22 16:47:12 +08:00
dd07ecc4b8
Externalize handling of command serialization
2022-03-22 16:47:12 +08:00
dd3c60f50e
Move request/response debug logging to client
2022-03-14 23:41:41 +08:00
ace791b521
Add test for dropping request future
2022-03-14 23:41:41 +08:00
ae4c9869ab
Improve robustness against dropping futures
2022-03-14 23:41:41 +08:00
478e686f24
Add more logging around reconnects
2022-03-14 23:41:41 +08:00
aa589197a1
Track connection state and reconnect on invalid state
...
The external client/connection interface expects that to complete
full request/response cycles. However, at await points the stack
could simply be dropped, meaning the connection is left in an
inconsistent state. One relatively likely scenario is that a
transaction might be dropped while waiting for a response from the
server. For example, this might happen if the connection was
initiated by a HTTP request which was canceled/aborted.
There are different failure modes which can result from similar
scenarios depending on during what await point the future was
dropped. Since it's relatively difficult to protect against
these scenarios and some of them might manifest in indirect ways
(for example, a deserialization error might happen because the
incoming response was for a different kind of request), this PR
takes the approach of tracking in the connection whether we're
(supposedly) at a point where the connection is ready to send
another request. If transact() is called while the connection is
not in such a state, the connection will transparently attempt
to reconnect to clean up any erroneous state.
2022-03-07 21:51:00 +01:00
7e0a51bebb
Use DateTime types where possible
2022-02-25 00:12:48 +08:00
f7d76adef3
Implement AsRef<str> for StringValue
2022-02-25 00:12:48 +08:00
cdbf0a2e65
Replace HostAddr with IpAddr in the public interface
2022-02-16 02:19:47 +08:00
1426312df0
Derive Debug for RequestData
2022-02-10 13:55:34 +08:00
af69f511b5
Generate error events for deserialization failures
2022-02-10 13:55:34 +08:00
53c240be21
Derive Copy on RequestData
2022-02-10 13:55:34 +08:00
386638b6ca
Offer API to reconnect an EppClient
2022-02-10 13:55:34 +08:00
36558c429c
Allow the Connection to connect itself
2022-02-10 13:55:34 +08:00
95b62891c9
Fix rustdoc warning
2022-02-04 11:39:13 +08:00
88eb9b9cab
Simplify/improve crate-level documentation
2022-02-04 11:39:13 +08:00
e482cc152b
Deduplicate client example code
2022-02-04 11:39:13 +08:00
dc3f10cae3
Wrap timeouts around network operations
2022-02-04 11:39:13 +08:00
f3aab578e7
Relax lifetime constraints on command + extension combinations
...
They should not be required to have the same lifetimes.
2022-01-31 14:05:52 +08:00
2639ec8c95
Make the Period type align with the standard
2022-01-31 14:05:16 +08:00
5fb32978bd
Improve check request API types by redirecting serialization
2022-01-31 14:04:48 +08:00
fdec3f29fc
Redirect CheckResponse deserialization to improve interface
2022-01-31 14:04:48 +08:00
a5d6643d6f
Share CheckResponse type with contacts
2022-01-31 14:04:48 +08:00
dd1c9c1e66
Share CheckResponse types for domain and host resources
2022-01-31 14:04:48 +08:00
999149ba31
Share the Available type across domain and host
2022-01-31 14:04:48 +08:00
a6dfe70361
Use bool for availability for contact/host resources as well
2022-01-31 14:04:48 +08:00
0c36d8add3
Use an enum for result codes
2022-01-27 17:10:28 +08:00
630c6b06e4
Change DomainAvailable::available to be a bool
...
From RFC 5731:
This element MUST contain an "avail" attribute whose value indicates
object availability (can it be provisioned or not) at the moment the
<check> command was completed. A value of "1" or "true" means that
the object can be provisioned. A value of "0" or "false" means that
the object can not be provisioned.
2022-01-24 16:34:33 +08:00
9acd9eac29
Take Login ext_uris values as a slice to allow caller to avoid allocation
...
In some cases the caller might be able to use a const slice for this.
2022-01-24 15:34:45 +08:00
58b72f9b0c
Make sure Error implements Send and Sync
2022-01-23 23:34:58 +08:00
4615d63b13
Make it possible to create hosts without addresses
2022-01-19 23:29:55 +08:00
c0ebbf6b52
Add test case for message only poll response
2022-01-06 19:22:20 +08:00
427db7a1eb
Add test case for empty queue poll response
2022-01-06 19:22:20 +08:00
569bd86bae
Add HostInfoResponseData to list of support message poll response types
2022-01-06 19:22:20 +08:00
4f112469ce
Re-use DomainTransferResponseData in message poll
2022-01-06 19:22:20 +08:00
24356a722a
Re-export command types for easier access
2022-01-03 10:29:58 +08:00
e9c5db9a1c
Add basic test for high-level API
2022-01-03 10:22:20 +08:00
0cd3e28b22
Use get_epp_response() to read initial greeting
2022-01-03 10:22:20 +08:00
8efb206e43
Rename test directory to tests
2022-01-03 10:22:20 +08:00
70f3789098
Make tokio-rustls dependency optional
2022-01-03 10:22:20 +08:00
0db2c6d008
Abstract EppClient over stream type
2022-01-03 10:22:20 +08:00
44f3fbef53
Move responsibility for stream setup into client
2022-01-03 10:22:20 +08:00
d69439ff24
Abstract EppConnection over stream type
2022-01-03 10:22:20 +08:00
3d0c3166f3
More concise/consistent error messages
2021-12-27 15:29:09 +08:00
978e43a4c1
Consistently return Error type
2021-12-27 15:29:09 +08:00
abab1aca8c
Store richer Box<dyn StdError> in Error::Other
2021-12-27 15:29:09 +08:00
6d063804d3
Use consistent naming for error types
2021-12-27 15:29:09 +08:00
Dirkjan Ochtman
Nicholas Rempel