On Apr 25, 2007, at 6:18 PM, Yi Qiang wrote: > On Apr 25, 2007, at 4:49 PM, Justin C. Walker wrote: > >> On Apr 25, 2007, at 13:28 , alex clemesha wrote: >> >> Having said that, might it be a good idea to allow 'locking' of this >> feature (perhaps with password protection)? I can foresee situations >> in which this would be useful. > I think a easy solution would be to be able to have 'private' jobs. > I.E. the job_id column would just show 'PRIVATE'. If you knew the > job id you can just put it into the the search box alex already > made. That was the reason job ids were random to begin with anyways. > > What do you think of this solution?
First, let me say that this dsage job page is pretty cool. About the random job ids, sounds like "security through obscurity" to me. There's already the concept of job ownership, and levels of trust controlling who can submit/process a job, so I think (long term at least) that infrastructure could be used to control viewing (or even showing up in the list). --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
