> On Thu, Feb 3, 2011 at 7:17 AM, eRobot wrote: > > Thats a good point Dave, I could create a separate app for this as > they will > > not need to see my web app, they only need to see the image and click > a > > radio button to approve or not. > > > > Would you recommend a login approach or some kind of temporary url. > > I need security but would like to avoid issuing login details? > > Easiest would be to generate some sort of GUID associated with the > picture and email the person a link to it. You could either use a GUID > per photo, or per user, or whatever. > > It ain't perfect, but it might be "good enough", at least if you have > email addresses.
You can always have a simple web application that allows a set of people to display what images are pending approval and they could drill down into each request and select their approval option. If you need to secure the records because only certain users can approve certain images under specific scenarios, then you could build this logic into the application. If anyone can approve anything but you still want to secure the application to insure that only the "approvers" are doing this process, you could share a common set of credentials with them all if knowing who does the activity is of no concern. Dave's solution would work too and if necessary, you could have your GUID generation process regenerate a valid GUID for each image on an interval so that if the image isn't approved within X time period, the old link is invalid if that is of any concern. Chris --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
