Comments on: Rounded Corners in Rails http://furui.org/blog/2006/12/18/rounded-corners-in-rails/ Jeff's Log Sat, 06 Jan 2007 05:30:57 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: furui http://furui.org/blog/2006/12/18/rounded-corners-in-rails/#comment-33 furui Sat, 06 Jan 2007 05:30:57 +0000 http://furui.org/blog/2006/12/18/rounded-corners-in-rails/#comment-33 @Octoberdan, Ah, right. I'll update the code to set a limit when I get a chance. Thanks a lot! Hmm, strange. I first tested the javascript anti-spam plugin with Firefox 2.0.0.1. I'll try it with 1.5 later and if it doesn't work, I'll pull it. @Octoberdan,
Ah, right. I’ll update the code to set a limit when I get a chance. Thanks a lot!

Hmm, strange. I first tested the javascript anti-spam plugin with Firefox 2.0.0.1. I’ll try it with 1.5 later and if it doesn’t work, I’ll pull it.

]]> By: Octoberdan http://furui.org/blog/2006/12/18/rounded-corners-in-rails/#comment-32 Octoberdan Sat, 06 Jan 2007 00:45:53 +0000 http://furui.org/blog/2006/12/18/rounded-corners-in-rails/#comment-32 Perhaps you should add validation and reject requests for obscenely large and therefore strenuous images. If this process continues to reside within and be offered by a controller, which is inherently publicly accessible, then a malicious user with ill intent could theoretically write a script that fires off thousands of requests for large images and create heavy lag if not crash something... And if you implement caching and neglect protection from abuse, then that person could change their script to loop with "w=#{n++}" and cause further trouble. I'm going to try out your code and see if I can exploit it while its on my server. I'll report my findings... And by the way, I had to use Internet Explorer to post this comment, Firefox didn't pass the "javascript test!" Perhaps you should add validation and reject requests for obscenely large and therefore strenuous images. If this process continues to reside within and be offered by a controller, which is inherently publicly accessible, then a malicious user with ill intent could theoretically write a script that fires off thousands of requests for large images and create heavy lag if not crash something… And if you implement caching and neglect protection from abuse, then that person could change their script to loop with “w=#{n++}” and cause further trouble. I’m going to try out your code and see if I can exploit it while its on my server. I’ll report my findings… And by the way, I had to use Internet Explorer to post this comment, Firefox didn’t pass the “javascript test!”

]]> By: furui http://furui.org/blog/2006/12/18/rounded-corners-in-rails/#comment-9 furui Tue, 19 Dec 2006 03:17:10 +0000 http://furui.org/blog/2006/12/18/rounded-corners-in-rails/#comment-9 @Jaime, To use it, your server must support Ruby on Rails: http://www.rubyonrails.org/ It must also have the RMagick gem installed: http://rmagick.rubyforge.org/ The controller must be installed into a Rails application. The image file is not necessary. The script generates the image on the fly. @Jacob, I am going to experiment with fragment caching when the project I am working on approaches beta. At that time, I'll probably post an updated version of this snippet. This was a rough and fast throw together implementation. @Jaime, To use it, your server must support Ruby on Rails: http://www.rubyonrails.org/

It must also have the RMagick gem installed: http://rmagick.rubyforge.org/

The controller must be installed into a Rails application.

The image file is not necessary. The script generates the image on the fly.

@Jacob, I am going to experiment with fragment caching when the project I am working on approaches beta. At that time, I’ll probably post an updated version of this snippet. This was a rough and fast throw together implementation.

]]> By: Jacob Radford http://furui.org/blog/2006/12/18/rounded-corners-in-rails/#comment-8 Jacob Radford Mon, 18 Dec 2006 23:52:29 +0000 http://furui.org/blog/2006/12/18/rounded-corners-in-rails/#comment-8 Can you take advantage of caching? Then the cost will only hurt on the first call, right? Can you take advantage of caching? Then the cost will only hurt on the first call, right?

]]> By: Jaime Lassman http://furui.org/blog/2006/12/18/rounded-corners-in-rails/#comment-7 Jaime Lassman Mon, 18 Dec 2006 19:55:33 +0000 http://furui.org/blog/2006/12/18/rounded-corners-in-rails/#comment-7 What do I need to do to get this to work on my own server? If I copy the image and the ruby controller, I can't make it work. What am I missing? image http://www.myserver.com/corners/roundedcorners.png controller file=http://www.myserver.com/corners/tools_controller.rb the URL http://www.myserver.com/corners/roundedcorners?c=999999&bc=white&w=50&h=50&a=tr gives an error. What am I missing? What do I need to do to get this to work on my own server? If I copy the image and the ruby controller, I can’t make it work. What am I missing?

image http://www.myserver.com/corners/roundedcorners.png

controller file=http://www.myserver.com/corners/tools_controller.rb

the URL http://www.myserver.com/corners/roundedcorners?c=999999&bc=white&w=50&h=50&a=tr gives an error. What am I missing?

]]> By: furui http://furui.org/blog/2006/12/18/rounded-corners-in-rails/#comment-6 furui Mon, 18 Dec 2006 17:57:12 +0000 http://furui.org/blog/2006/12/18/rounded-corners-in-rails/#comment-6 @Derek, That's a good idea. I might rewrite it as a simple plugin or something, though. It's a quick hack, actually. @Martin, In development mode running on a 2.2 GHz Opteron with 512 MB of ram on FreeBSD 6.1 AMD64 via Mongrel, it takes 0.0242~ seconds to completely process each rounded corner. Or, so the logs say. So, that much extra time for each rounded corner. Processing ToolsController#roundedcorners (for 64.xxx.xxx.xxx at 2006-12-18 00:19:13) [GET] Session ID: xxx Parameters: {"a"=>"tr", "w"=>"50", "bc"=>"red", "c"=>"999999", "action"=>"roundedcorners", "controller"=>"tools", "h"=>"50"} Rendering tools/roundedcorners Sending data Completed in 0.02423 (41 reqs/sec) | Rendering: 0.00005 (0%) | 200 OK @Derek, That’s a good idea. I might rewrite it as a simple plugin or something, though. It’s a quick hack, actually.

@Martin, In development mode running on a 2.2 GHz Opteron with 512 MB of ram on FreeBSD 6.1 AMD64 via Mongrel, it takes 0.0242~ seconds to completely process each rounded corner. Or, so the logs say. So, that much extra time for each rounded corner.

Processing ToolsController#roundedcorners (for 64.xxx.xxx.xxx at 2006-12-18 00:19:13) [GET]
Session ID: xxx
Parameters: {“a”=>”tr”, “w”=>”50″, “bc”=>”red”, “c”=>”999999″, “action”=>”roundedcorners”, “controller”=>”tools”, “h”=>”50″}
Rendering tools/roundedcorners
Sending data
Completed in 0.02423 (41 reqs/sec) | Rendering: 0.00005 (0%) | 200 OK

]]> By: Martin Smith http://furui.org/blog/2006/12/18/rounded-corners-in-rails/#comment-5 Martin Smith Mon, 18 Dec 2006 15:17:58 +0000 http://furui.org/blog/2006/12/18/rounded-corners-in-rails/#comment-5 Hi, How much extra processing does this take, compared to the same page without the corners? Martin Hi,

How much extra processing does this take, compared to the same page without the corners?

Martin

]]> By: Derek http://furui.org/blog/2006/12/18/rounded-corners-in-rails/#comment-4 Derek Mon, 18 Dec 2006 14:21:06 +0000 http://furui.org/blog/2006/12/18/rounded-corners-in-rails/#comment-4 I've yet to test this out, but it looks interesting. Here's a nitpicky concern: how come you didn't create this as a helper instead of a controller action? I’ve yet to test this out, but it looks interesting.

Here’s a nitpicky concern: how come you didn’t create this as a helper instead of a controller action?

]]>