Nick Kew wrote: >> I agree with the above. I started this thread to make people aware of >> it's existance and to provoke discussion on the matter. > > Yep, someone posted it a week or so back. Yeah, me. >> However, if someone were to take up the reigns and begin >> developing an Apache module for it using the open source code and >> specs Google has published, I think the project has a more serious >> chance of succeeding. I also think that an Apache with SPDY support >> available before the spec is finalised would be in a stronger position >> to influence how the protocol evolves during it's development. > > Apache works mostly on a "scratch your own itch" basis, so that depends > on whether anyone is sufficiently interested. > > Of course, if google is sufficiently interested, they have the > capability to produce a module! Yes, of course. >> I also wonder if a transition like this to a new protocol could/should >> be taken advantage of to get rid of the one SSL cert per IP:port >> limitation we currently suffer from? > > We dispensed with that limitation in (IIRC) 2.2.12. See the change log. As I understand it, you can't just stick multiple SSL sites on a single IP:port atm without excluding all clients that don't support SNI. The point I was trying to make was that something like SNI should be a requirement in SPDY rather than just optional, otherwise we could end up in the situation where some SPDY clients support SNI and others don't, which I'm sure nobody wants. -- Mike Cardwell - IT Consultant and LAMP developer Cardwell IT Ltd. (UK Reg'd Company #06920226) http://cardwellit.com/ Technical Blog: https://secure.grepular.com/blog/ --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|