By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,190 Members | 1,555 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,190 IT Pros & Developers. It's quick & easy.

Tracking Recent Downloads

P: n/a
Hi All,

I'm working on a project which requires tracking of recent document
downloads. There is a feature in which user can download the docs
without logining into the website for some of the clients. While for
other clients user has to log into the website to download docs.

We used to create dummy/fake accounts(in sql server) for client users
who do not require login and use the created account to track recent
downloads(using cookie to store the dummy/fake account id). But now we
realize that creating dummy/fake account each time when the cookie is
deleted can cause problems like user table will grow big because of
dummy/fake accounts.

Any suggestions on this?

Thanks.

Jan 8 '07 #1
Share this Question
Share on Google+
2 Replies


P: n/a
What kind of tracking are you looking for? One of the simplest tracking
mechanisms is instead of linking directly to a file, you link to an
intermediate file and pass the URL of the download file as a parameter. This
intermediate file, which we'll call download.aspx for now, can then save any
info about the user available into a database then redirect the user to the
url of the download item that was passed in as a parameter. This was you can
grab their IP address, browser type, etc..
--

Hope this helps,
Mark Fitzpatrick
Former Microsoft FrontPage MVP 199?-2006
"C# programmer" <sh********@gmail.comwrote in message
news:11**********************@v33g2000cwv.googlegr oups.com...
Hi All,

I'm working on a project which requires tracking of recent document
downloads. There is a feature in which user can download the docs
without logining into the website for some of the clients. While for
other clients user has to log into the website to download docs.

We used to create dummy/fake accounts(in sql server) for client users
who do not require login and use the created account to track recent
downloads(using cookie to store the dummy/fake account id). But now we
realize that creating dummy/fake account each time when the cookie is
deleted can cause problems like user table will grow big because of
dummy/fake accounts.

Any suggestions on this?

Thanks.

Jan 8 '07 #2

P: n/a
Thanks for the response Mark.

The tracking should be similar to the "Recently visited groups" in
google groups. If you log into groups.google.com you will have the list
of groups you visited recently. But if you log out then you will have
different list of groups which you visited while you were not logged
in.

Now when the user is not logged in, how can we identify the user to
keep track of the recently visited groups.

Let me know if you have any questions.

Thanks.
Mark Fitzpatrick wrote:
What kind of tracking are you looking for? One of the simplest tracking
mechanisms is instead of linking directly to a file, you link to an
intermediate file and pass the URL of the download file as a parameter. This
intermediate file, which we'll call download.aspx for now, can then save any
info about the user available into a database then redirect the user to the
url of the download item that was passed in as a parameter. This was you can
grab their IP address, browser type, etc..
--

Hope this helps,
Mark Fitzpatrick
Former Microsoft FrontPage MVP 199?-2006
"C# programmer" <sh********@gmail.comwrote in message
news:11**********************@v33g2000cwv.googlegr oups.com...
Hi All,

I'm working on a project which requires tracking of recent document
downloads. There is a feature in which user can download the docs
without logining into the website for some of the clients. While for
other clients user has to log into the website to download docs.

We used to create dummy/fake accounts(in sql server) for client users
who do not require login and use the created account to track recent
downloads(using cookie to store the dummy/fake account id). But now we
realize that creating dummy/fake account each time when the cookie is
deleted can cause problems like user table will grow big because of
dummy/fake accounts.

Any suggestions on this?

Thanks.
Jan 8 '07 #3

This discussion thread is closed

Replies have been disabled for this discussion.