* Updated wasm code to work with new gateway and updated the example
* cargo fmt
* Fixed test by ensuring destination is present at a gateway
* Updated hardcoded default port
* ibid. to correct value
* Some clippy and compiler warning fixes
* Removed healthchecker from the client
* Cargo fmt issue after 100 explicit saves.........
* Changes accidentally removed in previous PR
* Changed default listening port to something slightly more meaningful
* Removed TCP socket and made websocket the default option (as opposed to 'None')
* Updated template
* Updated ReceivedBuffer to allow direct message forwarding
* ignoring vscode directory
* Push messages mechanism for websocket client-clients
* Removed flawed chunking example
* ... but added bunch of websocket examples in return!
* Moves js example directory
* Cargo fmt
* Removed old listener code
* Initial draft for ClientsHandler
* Created listener struct
* typo
* Stateful websocket connection handler
* Exposing modules
* Depdendencies updates
* Moved listener to correct file + made start consume listener
* Main starting new listener
* Catching sigint
* Copied client storage from provider into gateway
* Exposed websocket listener type for nicer import path
* Defined websocket message receiver concrete type
* Client ledger struct without implementation
* ClientsHandler using more concrete types
* Mixnet sender + receiver and exposed listener type
* Handling mix packets
* Ability to forward mix packets
* "starting" both listeners at main
* Depedencies updates
* Initial type definitions for client messages
* Initial "gateway-requests" with AuthToken
* ibid.
* Restored most of ledger's functionalities
* Ability to retrieve all messages regardless of rate limit
* ClientsHandler request handling logic
* Required 'new' dependencies
* Main changes required for compilation
* PacketProcessor getting private key pointer
* "moved" types into gateway requests crate
* Moved and renamed types
* ibid.
* Added required serde_json dependency
* Skeleton for websocket request handling
* helper methods on ServerResponse
* WebSocket Handler pushing received mix messages directly to client
* PacketForwarder returning JoinHandle alongside the channel
* ClientsHandler following the same pattern
* Made websocket listener start method consistent with mix listener
* Syntax error + formatting
* Websocket handler having access to mix forwarder
* Minimal binary request parsing
* Implicitly derived std::error::Error on GatewayRequestsError
* Handling of all websocket requests
* Types import cleanup
* Updated placeholder fields
* Everything put into main
* Missing license notices
* Cleaned up unused code
* Copied and did initial minor changes to commands and config
* It's actually gateway
* Gateway sending its regular presence to directory server
* Re-organisation of gateway code + Gateway struct
* Updated provider argument description
* Restored duplicate ip check without importing NymTopology trait
* Moved hardcoded values into config
* Cargo fmt
* Compilation errors in other crates due to topology adjustments
* Test fixes
* Initial gateway-client
* Seemingly working version with bunch of hardcoded and temporary values
* cargo fmt
* Removed provider poller
* Updated config with gateway values instead of provider
* Gateway address including ws
* Removed hardcoded gateway address
* Properly skipping loop cover messages
* Updated log filter with tokio tungstenite related modules
* Updated sphinx version used
* Very minor cleanup
* unused import
* directory-client: removing explicit type definitions
* clients/webassembly: ugly commit, removes dependency on HTTP crates
...at the cost of copying quite a bit of NymTopology-related stuff into
the WebAssembly client. I'll make an issue to refactor that later.
* A more helpful hint in the error message when websocket connection fails.
* Removing superfluous JavaScript, route checking now happens in Rust
* Moved `nym-sphinx-wasm` into `wasm` folder and renamed its examples
* A proposal for some structural cleanup
* desktop client: beginning of a Rust example for chunking.
* Simplifying desktop client readme
* Tarting up webassembly README
* A more visual webassembly client example
* clients/webassembly: grouping a few things into named functions for clarity
* clients/webassembly: put URLs at top of file, prepping for drop-down action
* mixnode + provider run: changed startup error messages a bit
* clients/webassembly: scrolling from the bottom in the demo
Jędrzej Stuczyński