[Seaside-dev] Issue 3 in seaside: A RESTful configuration editor would be very useful

[codesite-noreply at google.com]

Issue 3: A RESTful configuration editor would be very useful
http://code.google.com/p/seaside/issues/detail?id=3

Comment #6 by philippe.marschall:
Guys I hope you are not serious about this code. #initialRequest: alone 
as several
problems.
1. It sends #asString which is no longer supported
2. It sends #asString. #asString converts the URL to a full URL which 
may include
the scheme. Then it tries to pase the path again. This will fail in the 
case of a
full URL with a scheme. Second it is schizophrenic because WAUrl aleady 
has a path.

Sorry guys, but this is not acceptable code quality.

So what should you do IMHO:
- Make methods in WAUrl that do the path computation
- Write tests!
- Use those tested methods.


Issue attribute updates:
	Status: Started

-- 
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings