“Magic links” are a different approach. Instead of a single, long-lived password, the web app generates a new, unique secret code every time you want to login. The web app then sends you an email or an SMS with a link to login. This link contains this unique secret code: your short-lived shared secret.
https://blog.approveapi.com/tutorials/rust-actix-web-approveapi-magic-login-link/
Además de la presentación del juego es muy interesante la discusión y los comentarios sobre la distinción Actors != Agents.
CityBound – an open source city simulation game in Rust (and using actors) from programming
Si programas en Rust con Visual Studio Code ya sabrás que se ha liberado la version 0.4.2 de la extensión crates corrigiendo algunos errores. https://t.co/OPXngLdegK
The actix framework handles requests asynchronously, but in this case the handlers themselves are not implemented asynchronously, for example using futures. I decided to keep it simple at first.
On the Rust side of things, just TCP is implemented in the Rust Core. The current web frameworks (actix and rocket) are implementing everything up until HTTP though. So you don’t need to care where this is coming from.
If you want to use pure HTTP calls without any larger framework, you can install “crates” (equivalent to npm packages in the Node world) which implement the HTTP protocol (like hyper and tiny_http).
Asynchronous programming is a concept which allows not blocking the program workflow when waiting for the results of certain actions. So you can open a large file or query a database, but your program will continue processing each line afterwards.
Diesel seems to be the only real database abstraction layer that is in a real state of completion. The problem is, though, following their guide (even when using new package import style) just results in missing macro errors for the generated schema file. After adding the «public» macro use statements, I just get more missing errors for «private» macros.
Is there any practical way of using Diesel with (stable) Rust 2018, or do I just have to wait for their next major release to be able to use Diesel?
Is it possible to use Diesel schema macros with Rust 2018? from rust
