PXRequestLog

Can you please clarify step #2 below regarding PXRequestLog ?

Is it <category name=org.pixory.PXRequestLog....>

Thanks.
Hemant.


--- In [email protected], Gunnar Heikkilä <pixory@u...> 
wrote:
> 
> > You can't. Hits logging is not yet implemented.
> > 
> 
> On the other hand it is super-easy to do your own logging. Just edit
> the  "log.configuration.xml" file sligthly and then create the log 
by
> e.g. a Perl script. If you also want to get the names of the public
> users you can add your own entry-page to catch that.
> 
> Step 1: Change the time stamp in the logging so that date is added:
> "ConversionPattern" value="%d{yyyy-MM-dd HH:mm:ss,SSS} (%t) [%p:%c
{2}
> -- %m]%n"
> 
> Step 2: Change the value of "PXRequestLog" to priority 
value="debug".
> Set all others to "error" to get smaller log files.
> 
> Step 3: Create a HTML page with a form (I use First name, Last name,
> Email) which users are required to fill in before they can be
> redirected to your Pixory site. Add the name and email as parameters
> to the Pixory HTTP request (e.g.
> http://xxx.xxx.xxx.xxx:8081?firstname=AAAA&lastname=BBBB&email=CCCC)
> so that this info will be in the log file.
> 
> Step 4: Create a small script which parses through the log files and
> extracts whatever you want to know. I find it easiest to let the
> script produce an HTML page with the following information for each
> user accessing Pixory:
> 
> 2004-09-15 14:00:30 [194.xxx.yyy.24]  Firstname Lastname Email
> 
> Album name
> 
> Then follows all pictures that user has viewed. I let the HTML page
> point to the smallest thumbnails (75 pixels) for pictures only 
viewed
> in "thumbnail mode", and point to the larger 150 pixel thumbnail for
> pictures which the user actually viewed separately. 
> 
> 2004-09-16 14:00:30 [194.xxx.yyy.24]  Firstname Lastname Email
> 
> Album name
> 
> Pictures...
> 
> 
> Then I just use my browser to actually "watch" the pictures my user
> watched. I have used this method since Pixory 2.12, and it works 
good
> enough for me. Of course I cannot stop anyone from filling in a fake
> name, but that has rarely been any problem.
> 
> A sligth drawback is that if more than one user is looking at the
> pictures at the same time, and both users have the same IP address
> (typical my collegues at my company) it will not be possible to know
> exactly who is watching what picture. 
> 
> I also use the "entry page" to say some words about my picture site
> (usual disclaimers etc.), plus warn that my server is not always
> running. To avoid that people create bookmarks directly to my Pixory
> site I let the entry page open Pixory in a new window without any
> toolbar info (e.g.
> 
toolbar=no,location=no,directories=no,status=no,menubar=no,scrollbars=
yes,resizable=yes).
> I also use cookies to remember their form input to make next access
> easier for them (and thus encourage that the form is filled-in every
> time).
> 
> Joe, if you are going to implement some kind of user logging, then 
you
> could consider the following scheme to handle public user tracking:
> 
> Specify a number of "special parameters" which can be added in any
> http request in Pixory. E.g. "pixory1, pixory2, ..., pixory5". If 
any
> of these parameters are found in the http request, then Pixory 
should
> keep adding the same paramaters to all subsequent http requests.
> 
> In this way it would be very easy to trace individual accesses, even
> when made by public users. I can catch the names by a form, and then
> send in the parameters the same way as I do today. If this was
> implemented there would no longer be a problem with users behind the
> same proxy.
> 
> /Gunnar





 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/pixory-beta/

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/