Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implementation of a servlet filter using the library would be nice #17

Open
GoogleCodeExporter opened this issue Apr 20, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link

Attached is a draft of a servlet implementation that can handle image 
resizing. It is working but I'm still working on a caching mechanism that 
would prevent the recreation of the thumbnails

I've used the latest svn version

Original issue reported on code.google.com by [email protected] on 16 Mar 2010 at 2:26

Attachments:

@GoogleCodeExporter
Copy link
Author

I think the servlet is a little outside the scope of the project. However I'm 
sure that 
your servlet will be appreciated by the users of the library, so maybe I'll 
create an zip 
file with example usage.

I must say that I was impressed with your work. I think you have a very clear 
way of 
writing source code.

For the caching part, I suggest that you take a look at EHCache (or the JSR107 
JCACHE API).

Original comment by m%[email protected] on 20 Mar 2010 at 7:50

@GoogleCodeExporter
Copy link
Author

Original comment by m%[email protected] on 20 Mar 2010 at 7:51

  • Added labels: Type-Enhancement
  • Removed labels: Type-Defect

@GoogleCodeExporter
Copy link
Author

Thanks, You can use the code provided as you wish!

By the way, I was looking at a JSR107 based solution witch could fall back to a 
simple 
disk persistence based cache in case of no jsr107 implementation.

I think it becomes a little bit bigger than a simple java file implementing a 
Servlet 
:-) 

Original comment by [email protected] on 21 Mar 2010 at 7:36

@GoogleCodeExporter
Copy link
Author

Thanks again :-)

I think I'll add the servlet you created pretty much as it is, and then point 
out that it 
must add some kind of cache mechanism to be useful in a production environment. 
Adding a cache is absolutely required, but it also spoils the simplicity of the 
servlet.

I'll add the servlet in the next release. Maybe in it's own file.

Original comment by m%[email protected] on 21 Mar 2010 at 7:42

  • Changed state: Accepted

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant