pub enum WampErrorUri {
Show 28 variants
NotAuthorized,
ProcedureAlreadyExists,
NoSuchRealm,
ProtocolViolation,
NoSuchSubscription,
NoSuchRegistration,
InvalidUri,
NoSuchProcedure,
InvalidArgument,
Canceled,
PayloadSizeExceeded,
FeatureNotSupported,
Timeout,
Unavailable,
NoAvailableCallee,
DiscloseMeNotAllowed,
OptionDisallowedDiscloseMe,
NoMatchingAuthMethod,
NoSuchRole,
NoSuchPrincipal,
AuthenticationDenied,
AuthenticationFailed,
AuthenticationRequired,
AuthorizationDenied,
AuthorizationFailed,
AuthorizationRequired,
NetworkFailure,
OptionNotAllowed,
}Expand description
§[TODO]: WampErrorUri
Unimplemented, unfortunately this does absolutely nothing in the current moment. The reasons are described below.
§The Problem
Wamp URI’s have a variable amount of error URIs that get sent with different enabled features on wamp routers. This leads to the possibility of also running into “unknown errors”. This is running with the assumption that we add in each string manually to serde to parse the error to the enum variant.
Which, also isnt how the wamp protocol defines how to parse URIs. While I understand from the documents that URIs are parsed using Regex, I have gotten extremely inconsistent results while testing with errors using Regex to parse URIs.
To further explain, while there is some level of structure to the Regex they use in reference to what type of URI it takes, and I have modeled that into a rust like structure, using the Regex on actual URI’s from the wamp protocol returns very mixed (and almost always wrong on edge cases) results.
I will stop documenting here to cite myself, more investigation is needed.