permissioned.
regards,
Peter
- Original Message -
From: Onno Scheffers o...@piraya.nl
To: Tapestry users users@tapestry.apache.org
Sent: Wednesday, 10 June, 2009 19:19:21 GMT +02:00 Athens, Beirut, Bucharest,
Istanbul
Subject: Re: t5: protecting data from public access
this is a good
Hi,
In a app that I'm going to develop, it requires users to log in before they
can browse job related info, quite a number of those are pictures, those
photos now are stored in folders of the server, the easiest way is, link
that folder to tomcat's context, and program can refer to a
Hi Angelo,
you might investigate tapestry-spring-security [1]. It has everything
you need and there is a snapshot [2] that works with T5.1.
You can secure resources and if someone requests a secured resource
authentication is required from the framework. So, no hacking possible.
Michael
On Wed, Jun 10, 2009 at 7:06 AM, Angelo Chenangelochen...@yahoo.com.hk wrote:
folder, but it will slow down the rendering, any idea how to meet this
requirement with tapestry 5?
If you need or want a pure Tapestry solution, use a dispatcher. By the
way, a dispatcher is possible a solution for
Hi,
I use dispatcher in some cases like logging and automatic logging of user
with cookie, but
how to use dispatcher in this context? any tips? how we expose the protected
data?
Angelo
Thiago H. de Paula Figueiredo wrote:
On Wed, Jun 10, 2009 at 7:06 AM, Angelo
I didn't fully understand your exact requirement. Should the photo's be
publicly accessible (as in published by the user) or do you need to be
logged in to be able to access the photo?
If public access it isn't allowed, you should move the photo's to a
protected folder and you can create a
Hi,
your understanding is correct, photos are under protected folders. and the
scaling will be a problem, but do you think it is good to store photo in the
database's blob field? and every rendering requires copying from database to
a temporary file?
Onno Scheffers-3 wrote:
I didn't fully
On Wed, Jun 10, 2009 at 12:14 PM, Angelo Chenangelochen...@yahoo.com.hk wrote:
Hi,
Hi!
and every rendering requires copying from database to
a temporary file?
You don't need to that. Just create a page that returns the image
wrapped in a StreamResponse.
--
Thiago
Hi,
your understanding is correct, photos are under protected folders. and the
scaling will be a problem, but do you think it is good to store photo in
the
database's blob field? and every rendering requires copying from database
to
a temporary file?
You can spool the data from a BLOB
this is a good idea. which one is faster:
returning the image as a stream or a direct link to a physical file in the
file system?
Onno Scheffers-3 wrote:
Hi,
your understanding is correct, photos are under protected folders. and
the
scaling will be a problem, but do you think it is good
this is a good idea. which one is faster:
returning the image as a stream or a direct link to a physical file in the
file system?
The physical file is much faster.
It just gets a little troublesome to keep all files in sync if your
application has to be distributed over multiple servers: a
11 matches
Mail list logo
