Hacker News Reader

Comment by zzmp | Hacker News Reader

The Iron team is here. Feel free to ask us anything!

Simple question. According to [1], middlewares are cloned for each request. Is there a good built-in way of accessing shared mutable data, such as a connection pool?

1: http://docs.ironframework.io/iron/trait.Middleware.html

I would guess `Arc<Mutex<T>>`, `Arc<RWLock<T>>` and `Arc<SomeConcurrentContainer>` would all work (cloning them is a ref-count - the handle gets copied, not the contents).

You are looking for https://github.com/iron/persistent, which offers two utility middleware for exactly this.

Very nice, thanks.

We have a middleware for that! You can look at http://github.com/iron/persistent, which does wrap an RWLock in an Arc. It also provides a struct to make your middleware Share, so you can do similar things.

We also have session, which works on a HashMap under an Arc, although it isolates the mutable data to a session, instead of sharing it across isolated requests.

I've been curious about the HTTP implementation, particularly considering that `rust-http` is in bugfix-only mode and `teepee` is still in design phase. Did you folks build it from scratch?

We built Iron on top of `rust-http`, but we're excited for `teepee` too, and there are a few others popping up as well.

Are you planning on lending assistance to Teepee? We are kind of in limbo in terms of http right now and it would be a shame for Teepee to turn out to be vapourware :(

(A hint for any folks experienced with http - this could be your chance to make lasting mark on the Rust ecosystem!)

Not that experienced, but enthusiastic -- does that count ;-)?

Teepee is getting back on track now; I just had a few weeks where I was unable to do much with it, but I started designing and developing things again yesterday.

Do you plan to support handling XML? I mean XSLT transformation, XPath routing, XQuery?

Please don't!

Reply on news.ycombinator.com