Rails - Mar 2006 - Konqueror Ajax update

I had been comparing IE and Firefox Ajax performance, and since I have a
couple of Unix boxes in my workshop, I threw Konqueror into the mix, and
reported here earlier today (or yesterday) that Konqueror ( 3.4.3) could
handle Ajax perfectly, at least as far as the simplest AWDWR Ajax example
(./example/index) was concerned.
It occurred to me to do a more grueling test.
I took the "periodically_call_remote" example (./example/periodic),
and
specified CGI::escapeHTML(`ps -ef | grep ruby`) in the "ps" action.
With "ps
-ef", I enjoyed an Ajax "top" in a browser!. I used the default
refresh rate
of 2
Since I have a Slackware box, and there is currently a client''s KUbuntu
box
in the workshop, I fired up two separate "localhost"
WEBrick''s, and ran
Firefox and Konqueror on both Linux boxes (with the XP Laptop having IE
trundling along, taking 30 seconds extra on each cycle but going strong).
Then, after just eight minutes, both Konqueror processes on the two boxes
(one Slackware, the other Debian/Kubuntu), crashed, almost simultaneously.
I reported the crash to Konqueror (enclosing the KDE Krash handler
Backtrace), and will report here if they send a patch.
Mozilla and the slowpoke IE (6.0 on XP) show no observable limit, still
going strong after several hours.

Victor Kane
http://awebfactory.com.ar

PS For all you Craiglist entrepeneurs seeking out the "quick learning"
hard
workers", I want you to know I''ve had over ten years experience in
Ruby on
Rails!!
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://wrath.rubyonrails.org/pipermail/rails/attachments/20060321/32e3edff/attachment.html

It seems I am not that original. When I went on the Konqueror bugzilla to
report what had occured, I saw that several similar bugs (crashing on
mir.aculous (sp?) site, etc. had already been posted, and, more importantly,
that the bug has been resolved in the current development release.
So, next release needs to be checked out again, for this great little
browser / file system explorer / multi-protocol file-sharer.

Victor Kane
http://awebfactory.com.ar

Message: 8
> Date: Tue, 21 Mar 2006 00:35:45 -0300
> From: "Victor Kane" <victorkane@gmail.com>
> Subject: [Rails] Konqueror Ajax update
> To: rails@lists.rubyonrails.org
> Message-ID:
>         <ff176450603201935s6b5dc63ct2172d73af7f7186c@mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I had been comparing IE and Firefox Ajax performance, and since I have a
> couple of Unix boxes in my workshop, I threw Konqueror into the mix, and
> reported here earlier today (or yesterday) that Konqueror ( 3.4.3) could
> handle Ajax perfectly, at least as far as the simplest AWDWR Ajax example
> (./example/index) was concerned.
> It occurred to me to do a more grueling test.
> I took the "periodically_call_remote" example
(./example/periodic), and
> specified CGI::escapeHTML(`ps -ef | grep ruby`) in the "ps"
action. With
> "ps
> -ef", I enjoyed an Ajax "top" in a browser!. I used the
default refresh
> rate
> of 2
> Since I have a Slackware box, and there is currently a client''s
KUbuntu
> box
> in the workshop, I fired up two separate "localhost"
WEBrick''s, and ran
> Firefox and Konqueror on both Linux boxes (with the XP Laptop having IE
> trundling along, taking 30 seconds extra on each cycle but going strong).
> Then, after just eight minutes, both Konqueror processes on the two boxes
> (one Slackware, the other Debian/Kubuntu), crashed, almost simultaneously.
> I reported the crash to Konqueror (enclosing the KDE Krash handler
> Backtrace), and will report here if they send a patch.
> Mozilla and the slowpoke IE (6.0 on XP) show no observable limit, still
> going strong after several hours.
>
> Victor Kane
> http://awebfactory.com.ar
>
> PS For all you Craiglist entrepeneurs seeking out the "quick
learning"
> hard
> workers", I want you to know I''ve had over ten years
experience in Ruby on
> Rails!!
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://wrath.rubyonrails.org/pipermail/rails/attachments/20060321/6e1c40b5/attachment.html