On Tue, Oct 16, 2007 at 04:06:46PM +0400, Oleg Pronin wrote:
> another problem is a lot of internet traffic for transferring absolute urls.
> I think uri_for should delete "http://domain"; from target url if requested
> host and target host (and protocols) are the same.
There was a lot of arguing
another problem is a lot of internet traffic for transferring absolute urls.
I think uri_for should delete "http://domain"; from target url if requested
host and target host (and protocols) are the same.
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http
On 10/12/2007 11:31 AM, Oleg Pronin wrote:
> I have a hundred of and a hundred of per
> page on 1-2mln hosts/day project.
>
> If your project is not under subfolder of some domain then there is no
> need to call
>
> instead of
> as they are both pointing to the same place.
>
I think best
I have a hundred of and a hundred of per page
on 1-2mln hosts/day project.
If your project is not under subfolder of some domain then there is no need
to call
instead of
as they are both pointing to the same place.
2007/10/12, Matt S Trout <[EMAIL PROTECTED]>:
> On Thu, Oct 11, 2007 at 02:51
On Thu, Oct 11, 2007 at 02:51:31AM +0400, Oleg Pronin wrote:
> If your project is heavy loaded then i think the best way is to write:
>
> or (easy to change):
>
> in Object:
> sub update_url {'/myapp/'.shift->id.'/update}
>
> because Catalyst.uri_for() still takes to much CPU to call it a hundre
Oleg Pronin wrote:
> If your project is heavy loaded then i think the best way is to write:
>
> or (easy to change):
>
> in Object:
> sub update_url {'/myapp/'.shift->id.'/update}
>
> because Catalyst.uri_for() still takes to much CPU to call it a hundred
> times per page.
>
>
If you really t
If your project is heavy loaded then i think the best way is to write:
or (easy to change):
in Object:
sub update_url {'/myapp/'.shift->id.'/update}
because Catalyst.uri_for() still takes to much CPU to call it a hundred
times per page.
2007/10/10, Cédric Bouvier <[EMAIL PROTECTED]>:
>
> Hello
On 10/10/07, Cédric Bouvier <[EMAIL PROTECTED]> wrote:
>
> Hello Catalysters,
>
> I just started playing with Chained Actions, and so far I have a setup
> like this:
>
> /myapp/*
> /myapp/*/update
> /myapp/*/update_do
>
> 'update' and 'update_do' being implemented in MyApp::C::Foo::upda
Hello Catalysters,
I just started playing with Chained Actions, and so far I have a setup
like this:
/myapp/*
/myapp/*/update
/myapp/*/update_do
'update' and 'update_do' being implemented in MyApp::C::Foo::update and
MyApp::C::Foo::update_do, respectively.
Now, in the that gets dis
