How to audit/log the print event of third party tool in asp.net application

Question

0.00/5 (No votes)

See more:

I am using HTML5 viewer using prizm content connect 8.4(third party tool) in my asp.net application to view the documents. How can I audit/log the documents printed using viewer in my asp.net application table. The printing of the document is completely taken care by viewer. I have .cs and .js files of the viewer to work the viewer in my application.

Posted 23-Nov-14 7:16am

Member 11257468

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

**Zoltán Zörgő** · Answer 1 · 2014-11-23T07:47:00

I don't know anything about the component you mention. Actually you can have anything on client side, you can not rely on it. Does not matter if you have js code or not (well, there is no way not having them as we sepak about web). But for the very same reason you need to have at least one web server on the other end. So the question is if you have control on that web server. If you do, you can either use the web server logs to see what the client downloaded (and ultimately viewed on that control) - or you can build your own content delivery mechanism to have full control over that content, and write the logs as you need. If the content is comuing from a server outside your control, than you won't be able to gather the information you want.