Configuring Peek using a Guest Login ...
rhrd71 - December 4, 2008 - 21:56
| Project: | Peek |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
First off, let me say that this is (almost) exactly the functionality I have been looking for. Took a quick test (Drupal 6.x) and found it works as mentioned.
But I expect that the overhead of creating a new login per peek (and purging those eventually) would be significant. And my site is all private with no Anonymous access.
Would it be possible to use a Guest Login for the peek generation.
Would be nice it we do not have to deal with Transient ID generation.
Please let me know if my understanding of this is incorrect.
#1
I think you're understanding of how it works is correct, but I'm not sure of your proposal.
It's certainly not the right tool for generating lots and lots of private access urls. If you've really got a lot, then it's really not going to be very private any more and you might as well use security by obsurity no? What sort of numbers are you talking about?
The tool was more intended for smaller sets of users, typically ones that would have more than one use (e.g. a client), and tends to be fairy paranoid, so creating individual accounts for each email that's going to be used is useful for tracking purposes. I imagine you could automate the purging of unused accounts if it got too many.
#2
Thanks for your response.
I do expect hundreds are private access urls for the content - and so was concerned about the maintenance overhead.
Was wondering if a URL could be generated by Peek that uses a cookie to enable auto login to the site (like some of the yahoo groups/picassa web etc. are doing) - the cookie could have a set expiration.
If this is not feasible, would it be possible:
1. To set a known prefix for all peek generated ids (peek_...)
2. And include a cleanup module to automate deletion of these through a cron like mechanism
Thanks again for this.