[Seaside] static resources and urls

[Kamil Kukura]

>
>
><snip>
>However, is there any reason they have to be?  Right now, a typical URL
>looks like
>
>/seaside/config/uNH6GCyDqrpA6Wlf/top/1/view
>
>however, what issues would arise if that changed to
>
>/seaside/config/view?session=uNH6GCyDqrpA6Wlf&txn=top&page=1
>
If I am not wrong, that is from CGI's encoding for key=value pairs. 
That's okay, though reminds me something sent by <form method="GET" ...>
Have thoughts about single separator such as:

/seaside/config/view?uNH6GCyDqrpA6Wlf.top.1
/seaside/config/view?uNH6GCyDqrpA6Wlf,top,1
/seaside/config/view?uNH6GCyDqrpA6Wlf:top:1

-- 
Kamil