[Kss-devel] New GET future

[Balazs Ree]

On Thu, 03 Jul 2008 23:50:41 +0400, Vladislav Vorobiev wrote:

> Hi,
> 
> Without kss.demo it works well now.
> 
> I  patched cacheability.js library for my own intention on line 187
> 
> // sending form
> /*VV            url = url + '?' + encoded;*/ url = url
> 
> Its attaches "?" on my URL. My URL already includes. Maybe it is not
> very good idea but possibly it would be well to implement some feature
> to turn of question mark on the and of URL. In some cases, that would
> certainly be useful.

Why does your url include a question mark? I think this is the problem.
You must add your parameters with KSS and not as part of the server 
action's name.

We need to put the question mark there, because "?" is obligatory in 
front of the parameters. We should omit the "?" in case there are no 
parameters at all, but that hardly makes any difference?
 
> Maybe it is not a very good idea, but possibly it would be nice to
> implement some feature to turn of question mark at the and of URL.

Can you explain why the question mark is so important in your use case? 


> In some cases this would certainly be useful. See tread with subject:
> turn off ?kukitTimeStamp

kukitTimeStamp is a different issue. I understand why some 
developers felt the need to get rid of it, but it was put there 
intentionally: to ensure requests are not cacheable, even in case of a 
foul browser and cache setup. However even if we omit it, POST requests 
are still (supposed to be) uncacheable, so maybe it was too much 
precaution on our side.

But since you brought up kukitTimeStamp: THe plugin action can 
actually take a "method" parameter. If you specify "POST" here, it will 
do POST requests the old way - but without the kukitTimeStamp. This would 
also become the built in way for KSS, in the future, if it works well.


-- 
Balazs Ree