blob: 8d97ff690de0b43f0e2df61c29681c5f297e9b42 (
plain) (
tree)
|
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML>
<HEAD>
<TITLE> [99s-extend] Proposal for Cowboy Routing
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Proposal%20for%20Cowboy%20Routing&In-Reply-To=%3C20121113141259.GB17626%40members.linode.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<style type="text/css">
pre {
white-space: pre-wrap; /* css-2.1, curent FF, Opera, Safari */
}
</style>
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="000007.html">
<LINK REL="Next" HREF="000009.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[99s-extend] Proposal for Cowboy Routing</H1>
<B>Thomas Allen</B>
<A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Proposal%20for%20Cowboy%20Routing&In-Reply-To=%3C20121113141259.GB17626%40members.linode.com%3E"
TITLE="[99s-extend] Proposal for Cowboy Routing">thomas at oinksoft.com
</A><BR>
<I>Tue Nov 13 15:12:59 CET 2012</I>
<P><UL>
<LI>Previous message: <A HREF="000007.html">[99s-extend] Proposal for Cowboy Routing
</A></li>
<LI>Next message: <A HREF="000009.html">[99s-extend] Proposal for Cowboy Routing
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#8">[ date ]</a>
<a href="thread.html#8">[ thread ]</a>
<a href="subject.html#8">[ subject ]</a>
<a href="author.html#8">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Tue, Nov 13, 2012 at 10:04:17AM +0100, Loïc Hoguin wrote:
><i> Hello!
</I>><i>
</I>><i> I have put my thoughts on routing at the following gist:
</I>><i>
</I>><i> <A HREF="https://gist.github.com/4064759">https://gist.github.com/4064759</A>
</I>><i>
</I>><i> Please comment or cry in terror if you're against it!
</I>
I think that this looks very good. The current router handles all of my
use cases, and this bit of sugar will definitely help to speed up
development.
As an aside, have you considered adding optional slash-add
functionality, so that /a/b will match "/a/b/"? This is pretty easy to
set up at the server level, but the front-line server doesn't know about
our dispatch rules and so it doesn't know if there is a matching
dispatch rule for the slash-added version of a given URL.
Thomas
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="000007.html">[99s-extend] Proposal for Cowboy Routing
</A></li>
<LI>Next message: <A HREF="000009.html">[99s-extend] Proposal for Cowboy Routing
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#8">[ date ]</a>
<a href="thread.html#8">[ thread ]</a>
<a href="subject.html#8">[ subject ]</a>
<a href="author.html#8">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://lists.ninenines.eu/listinfo/extend">More information about the Extend
mailing list</a><br>
</body></html>
|
