Hi, one way is to do it like google docs when you want to share your doc with other people for viewing only..generate link with unique key e.g. www.whatever.com/page/321fg6h4fgh321fdh654fh654fh/ You store the key in your DB and verify validity of the link. Then you can also restrict access to it, not every one is allowed to see it, right? And you can use this key to grant access to other subpages of page.
But also temporary account is solution too, but you should also restrict access to other pages. Radovan On 9. Mar., 10:31 h., Torsten Bronger <bron...@physik.rwth-aachen.de> wrote: > Hall chen! > > We create a central database for our research institute. One must > be logged-in in order to access any pages. Sometimes, however, it > is interesting to be able to send a deep link in an email to an > external collegue who doesn't have an account. > > The collegue should then be able to see the link, and a couple of > others (in particular, the embedded graphics). Thus, the sent link > must be connected with a set of pages it grants access to. > > How would you solve this? A session key in the query string? How > do I then propagate the query string to all the <a href> tags in the > page? > > Or is a dynamically generated account better? > > Is there a better way to identify the set of accessable pages than > by a set of URLs? > > Is there already middleware in existence that I could use? > > Tsch , > Torsten. > > -- > Torsten Bronger Jabber ID: torsten.bron...@jabber.rwth-aachen.de > orhttp://bronger-jmp.appspot.com -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
