Re: suggested syntax for channels

Alan Knowles wrote:

I'm not sure how problematic the & is in unix, I use it alot with wget/lynx, and know that I need to quote the string using it. I doubt that it would be used enough to be a big enough issue to justify much effort working around it.

Would you say using /foo=bar/nextfoo=nextbar instead of ?foo=bar&nextfoo=nextbar is much effort from the user perspective? From the implementation perspective, using / is pretty straightforward, using ?thing=val&next=nextval would be simpler, but it's a difference of about 2 lines of code. Fortunately, there is a single function that processes this, so changing it will not be a big deal. Greg