Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Tracking web pages

Status
Not open for further replies.

Erikxxx

Programmer
May 5, 2003
49
GB
Hi all,

I'm currently looking at technical solutions for a system that will present a number of training-courses to various
employees. The courses itself are currently written in standard HTML and are independent of each other. When a user login
they will be given a set of courses they signed up for.
One of the requirements and the one I'm having problem with is finding a technical solution to how to implement a
feature such as when an user logon to the system all pages will be marked as unvisited. As you click on each page
the status of the page changes to visited. I'm looking for some form of persistent storage here (db, xml etc) because the owner of
the system want to be able to see what pages a particular user has visited/not visited. It is also possible that new content will be added to a particular course and this should
also be reflected in terms of an unvist flag next time the user login. I'm planning to implement the system using Tomcat, servlets
and JSP's, probably with a back-end database to store user info etc.

If anyone could talk me through on a possible technical high level solution that would be much appreciated.

We are actually thinking of turning all the html pages into xml and then using XSLT to generate the output. I don't have a clue
how we would implement this feature in that case.

Also the system should coup with at least 200 users concurrently accessing the course material (I guess you have to take that in
consideration if you planning of generating html on-the-fly through XSLT).

Thanks
E
 
Well, XSLT has the advantage that, except the first time, the only traffic is data traffic (xml files) as the xsl files are cached and processed at client side.

I know very litte a about xml storage anyway.

The "unread" flag I guess it will be a checbok or something in your jsp that will get its value at generation time from the database using JDBC.

When the content is saved, the database shoudl be updated for all users to that content with "unread".

Not sure it this helps you.

Cheers,
Dian
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top