Re: Members register & gain access system

This WebDNA talk-list message is from

1998

It keeps the original formatting. numero = 18783
interpreted = N
texte = At 9:30 Uhr 10.07.1998, Dan Tryon wrote:>...after they have filled out a simple registration>form and we approve them...>...we will be recording how>often they come in and what documents they download.>...does anyone have anything similarIn short:A people.db which contains basically a unique ID, login-name andpassword. You enter the name and/or the password manually via the browser(single entries) or via a textfile (all at once). I recommend to installyour own user database for this application. You might store user data likeaddresses there too.A visits.db with user-ID, login_date, login_time and a field fordownloaded items. If one downloads a file, store his original user-ID inthis database, together with the download information.So you have two databases with all information, you can build statistics asyou like.If you install user tracking (means you carry their ID's through allpages), you can have a form for the login. If you don't have user tracking,you must use browser authorization. Both methods have advantages andbackdraws.1. User comes the first time and completes the registration form.2. One email to you with the data, a thank you to the user.3. You verify the data manually, create a new record in people.db and send a mail to the user.4. User comes, clicks on a link or button and writes his login.5. Search in the people.db if this user is permitted, if yes then store ID, date and time within visits.db - if not, present an error page and he can try again.6. He found an item, comes to the download-page and - click.7. Now store the name or url of the item in visits.db - but only if the field is still empty. Otherwise he actually wants to download a second item - then create a new record with all data. You get his name by asking the browser or (if you have tracked him) you know it from a hidden field or url-parameter and do a lookup with the ID in people.db8. Mail to user thank you for downloading.9. Now you send him to the real download link.That's it. Remember, that you need an action which tells you the wish todownload. For the download itself you have a link. If the user finallydecides not to download the file, this is bad luck - I do not know a wayyet to verify if a user downloads or cancels, but you have to store therecord before.Hope it helps for now,Peter__________________________________________Peter Ostry - po@ostry.com - www.ostry.comOstry & Partner - Ostry Internet SolutionsAuhofstrasse 29 A-1130 Vienna Austriafon ++43-1-8777454 fax ++43-1-8777454-21 Associated Messages, from the most recent to the oldest:

Re: Members register & gain access system (Angel Bennett 1998)
Re: Members register & gain access system (Peter Ostry 1998)
Members register & gain access system (Dan Tryon 1998)

At 9:30 Uhr 10.07.1998, Dan Tryon wrote:>...after they have filled out a simple registration>form and we approve them...>...we will be recording how>often they come in and what documents they download.>...does anyone have anything similarIn short:A people.db which contains basically a unique ID, login-name andpassword. You enter the name and/or the password manually via the browser(single entries) or via a textfile (all at once). I recommend to installyour own user database for this application. You might store user data likeaddresses there too.A visits.db with user-ID, login_date, login_time and a field fordownloaded items. If one downloads a file, store his original user-ID inthis database, together with the download information.So you have two databases with all information, you can build statistics asyou like.If you install user tracking (means you carry their ID's through allpages), you can have a form for the login. If you don't have user tracking,you must use browser authorization. Both methods have advantages andbackdraws.1. User comes the first time and completes the registration form.2. One email to you with the data, a thank you to the user.3. You verify the data manually, create a new record in people.db and send a mail to the user.4. User comes, clicks on a link or button and writes his login.5. Search in the people.db if this user is permitted, if yes then store ID, date and time within visits.db - if not, present an error page and he can try again.6. He found an item, comes to the download-page and - click.7. Now store the name or url of the item in visits.db - but only if the field is still empty. Otherwise he actually wants to download a second item - then create a new record with all data. You get his name by asking the browser or (if you have tracked him) you know it from a hidden field or url-parameter and do a lookup with the ID in people.db8. Mail to user thank you for downloading.9. Now you send him to the real download link.That's it. Remember, that you need an action which tells you the wish todownload. For the download itself you have a link. If the user finallydecides not to download the file, this is bad luck - I do not know a wayyet to verify if a user downloads or cancels, but you have to store therecord before.Hope it helps for now,Peter__________________________________________Peter Ostry - po@ostry.com - www.ostry.comOstry & Partner - Ostry Internet SolutionsAuhofstrasse 29 A-1130 Vienna Austriafon ++43-1-8777454 fax ++43-1-8777454-21 Peter Ostry

DOWNLOAD WEBDNA NOW!

Re: Members register & gain access system

1998

Top Articles:

Related Readings: