rwf2
/
Rocket
mirror of https://github.com/rwf2/Rocket.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
Rocket/lib/src/lib.rs

30 lines
530 B
Rust
Raw Normal View History

Cleaned up routing code. It's nearing completion! * Should be able to write a simple O(n) router using the collision functions. * Still need to split things up into multiple files.
2016-03-19 02:05:29 +00:00
#![feature(str_char)]
Cleaned up response -> split into files. Started form example. There's something going on with Hyper. When a 303 (see other) response is sent in response to a POST, the browser does a GET to the location header. Hyper somehow misreads the method parameter here, resulting in a route failer. I need to MITM the connection to see exactly what the browser is sending and what Hyper is receiving to see who's wrong.
2016-03-28 09:34:09 +00:00
#![feature(specialization)]
Cleaned up routing code. It's nearing completion! * Should be able to write a simple O(n) router using the collision functions. * Still need to split things up into multiple files.
2016-03-19 02:05:29 +00:00
Routing is functional! Sort-of. Pretty console colors. Okay, so, given a URI, we can figure out which route is corresponds to. Unfortunately, the handler is not yet part of that route, and we're not parsing the parameters from the path quite yet. But, we're almost there!
2016-03-21 09:22:22 +00:00
extern crate term_painter;
Rocket is almost operational! `routes!` macro complete. Here's what works so far: * The `route` decorator checks its inputs correctly. There's a nice utility for doing this, and it's working quite well at the moment. * The `route` decorator emits a `route_fn` and a `route_struct`. The `routes` * macro prepends the path terminator with the route struct prefix. The * `Rocket` library can read mount information (though not act on it properly just yet) and launch a server using Hyper.
2016-03-12 18:45:19 +00:00
extern crate hyper;
Major refactoring. Here's the idea: under the `Rocket` namespace should live things critical to writing simple Rocket apps: Request, Response, Error, etc. Nothing should be nested more than one level deep. Only items required for more complex things (implementing uncommon traits, etc.) should be nested one level deep. This commit is the first attempt at realizing this.
2016-04-01 23:54:53 +00:00
mod method;
mod error;
mod param;
mod router;
mod rocket;
Somewhat good infrastructure for params and responses. Can actually return strings and what-not from a route. Yay!
2016-03-17 08:57:04 +00:00
pub mod request;
Major refactoring. Here's the idea: under the `Rocket` namespace should live things critical to writing simple Rocket apps: Request, Response, Error, etc. Nothing should be nested more than one level deep. Only items required for more complex things (implementing uncommon traits, etc.) should be nested one level deep. This commit is the first attempt at realizing this.
2016-04-01 23:54:53 +00:00
pub mod response;
Rocket is almost operational! `routes!` macro complete. Here's what works so far: * The `route` decorator checks its inputs correctly. There's a nice utility for doing this, and it's working quite well at the moment. * The `route` decorator emits a `route_fn` and a `route_struct`. The `routes` * macro prepends the path terminator with the route struct prefix. The * `Rocket` library can read mount information (though not act on it properly just yet) and launch a server using Hyper.
2016-03-12 18:45:19 +00:00
Major refactoring. Merged two `Route` structure. Created `URI` and `URIBuf`.
2016-04-02 07:51:40 +00:00
pub mod handler {
use super::{Request, Response};
pub type Handler<'a> = fn(Request) -> Response<'a>;
}
Major refactoring. Here's the idea: under the `Rocket` namespace should live things critical to writing simple Rocket apps: Request, Response, Error, etc. Nothing should be nested more than one level deep. Only items required for more complex things (implementing uncommon traits, etc.) should be nested one level deep. This commit is the first attempt at realizing this.
2016-04-01 23:54:53 +00:00
pub use request::Request;
Rocket is almost operational! `routes!` macro complete. Here's what works so far: * The `route` decorator checks its inputs correctly. There's a nice utility for doing this, and it's working quite well at the moment. * The `route` decorator emits a `route_fn` and a `route_struct`. The `routes` * macro prepends the path terminator with the route struct prefix. The * `Rocket` library can read mount information (though not act on it properly just yet) and launch a server using Hyper.
2016-03-12 18:45:19 +00:00
pub use method::Method;
Major refactoring. Here's the idea: under the `Rocket` namespace should live things critical to writing simple Rocket apps: Request, Response, Error, etc. Nothing should be nested more than one level deep. Only items required for more complex things (implementing uncommon traits, etc.) should be nested one level deep. This commit is the first attempt at realizing this.
2016-04-01 23:54:53 +00:00
pub use response::{Response, Responder};
Rocket is almost operational! `routes!` macro complete. Here's what works so far: * The `route` decorator checks its inputs correctly. There's a nice utility for doing this, and it's working quite well at the moment. * The `route` decorator emits a `route_fn` and a `route_struct`. The `routes` * macro prepends the path terminator with the route struct prefix. The * `Rocket` library can read mount information (though not act on it properly just yet) and launch a server using Hyper.
2016-03-12 18:45:19 +00:00
pub use error::Error;
Somewhat good infrastructure for params and responses. Can actually return strings and what-not from a route. Yay!
2016-03-17 08:57:04 +00:00
pub use param::FromParam;
Major refactoring. Merged two `Route` structure. Created `URI` and `URIBuf`.
2016-04-02 07:51:40 +00:00
pub use router::{Router, Route};
Major refactoring. Here's the idea: under the `Rocket` namespace should live things critical to writing simple Rocket apps: Request, Response, Error, etc. Nothing should be nested more than one level deep. Only items required for more complex things (implementing uncommon traits, etc.) should be nested one level deep. This commit is the first attempt at realizing this.
2016-04-01 23:54:53 +00:00
pub use rocket::Rocket;
Major refactoring. Merged two `Route` structure. Created `URI` and `URIBuf`.
2016-04-02 07:51:40 +00:00
pub use handler::Handler;