Author Topic: Kill Webbugs: Another One  (Read 6510 times)

sidki3003

  • Sr. Member
  • ****
  • Posts: 476
    • ICQ Messenger -
    • AOL Instant Messenger -
    • Yahoo Instant Messenger -
    • View Profile
    • http://
    • Email
Kill Webbugs: Another One
« Reply #15 on: August 19, 2002, 06:03:29 PM »
TEggHead wrote:
quote:

What about an alternative to eDexter?

exe size around 60Kb
support for CGI
definable port
definable IP
also in SSL available (slighlty larger)
with source (Delphi)
windowless console app

in short, TinyWEB at http://www.ritlabs.com/tinyweb/


Looks nice but seems to be the same thing as with my webserver:
I don't see an option to serve requests with something else than an *.htm* doc.
The online help speaks about the NT/2K/XP PATHEXT environment variable but i'd feel a bit uncomfortable appending .GIF to it.


 
 

hpguru

  • Moderator
  • Sr. Member
  • *****
  • Posts: 257
    • ICQ Messenger -
    • AOL Instant Messenger -
    • Yahoo Instant Messenger -
    • View Profile
    • http://lightning.prohosting.com/~hpguru/
    • Email
Kill Webbugs: Another One
« Reply #16 on: August 19, 2002, 07:24:58 PM »
Actually I think eDexter is a better choice because when configured not to use images (on the disk) it serves it's own internal 1x1 transparent gif. Using any other web server that cannot cache content in ram means you still have to grab a file from the disk and if you are going to do that you may as well use k or local.ptron in your filters.

Facing each other,
a thousand miles apart.
Facing each other,
a thousand miles apart.

lnminente

  • Jr. Member
  • **
  • Posts: 73
    • ICQ Messenger -
    • AOL Instant Messenger -
    • Yahoo Instant Messenger -
    • View Profile
    • Email
Kill Webbugs: Another One
« Reply #17 on: August 19, 2002, 07:37:18 PM »
one suggestion and question:

Could you use a iframe instead of a gif image?

 
 

sidki3003

  • Sr. Member
  • ****
  • Posts: 476
    • ICQ Messenger -
    • AOL Instant Messenger -
    • Yahoo Instant Messenger -
    • View Profile
    • http://
    • Email
Kill Webbugs: Another One
« Reply #18 on: August 19, 2002, 08:33:15 PM »
Might work ... for those browsers that support iframes .. don't know though.
However, after thinking about it, loading of the replacement image should not be a real problem.
Since it's called lots of times it should be in the OS RAM cache anyway.


 
 

hpguru

  • Moderator
  • Sr. Member
  • *****
  • Posts: 257
    • ICQ Messenger -
    • AOL Instant Messenger -
    • Yahoo Instant Messenger -
    • View Profile
    • http://lightning.prohosting.com/~hpguru/
    • Email
Kill Webbugs: Another One
« Reply #19 on: August 19, 2002, 08:49:53 PM »
quote:

Since it's called lots of times it should be in the OS RAM cache anyway.



Unfortunately that's not the case. Monitoring file system activity with Sysinternals Filemon I can observe Proxo opening killed.html, killed.gif, etc.

Facing each other,
a thousand miles apart.
Facing each other,
a thousand miles apart.

sidki3003

  • Sr. Member
  • ****
  • Posts: 476
    • ICQ Messenger -
    • AOL Instant Messenger -
    • Yahoo Instant Messenger -
    • View Profile
    • http://
    • Email
Kill Webbugs: Another One
« Reply #20 on: August 19, 2002, 09:47:12 PM »
Hmm... looks to me as if FileMon also logs access to objects that are in the file system cache.
When i open a file in notepad the 2nd time, i see almost zero disk read activity in performance monitor.
When i then start FileMon and open that file the 3rd time, i see in the log all those hundreds of reads in the DLLs etc ...


 
 

hpguru

  • Moderator
  • Sr. Member
  • *****
  • Posts: 257
    • ICQ Messenger -
    • AOL Instant Messenger -
    • Yahoo Instant Messenger -
    • View Profile
    • http://lightning.prohosting.com/~hpguru/
    • Email
Kill Webbugs: Another One
« Reply #21 on: August 19, 2002, 11:30:13 PM »
I used the string "proxomitron.exe" as a filter in Filemon so I was observing only Proxo's accesses to the disk. What I did was to block the url "adv.foo.com/bar.gif" using k in a header filter. Proxo read the killed.gif file among other things each time I reloaded. By contrast eDexter only read it's ini file. No other eDexter disk accesses were logged by Filemon.

BTW I don't mean to give the impression that eDexter is better than Proxo. Rather the two working together are slightly more efficient than Proxo by itself.

Facing each other,
a thousand miles apart.
Facing each other,
a thousand miles apart.