Wt

Christophe,

That's the access log. You can redirect it to a file:

./myapp --accesslog logfile

or on unix to /dev/null to get completely rid of it:

./myapp --accesslog /dev/null

Wim,

By luck, if i use /dev/null on Windows, Wt does not manage to open the file and then writes nothing, which is exacly what i want !

Shouldn't there be a proper option to disable output ?

Regards

Christophe

I have the same problem. Is there any way to get a 'silent' timer and not to completely disable access log?

Alan,

What do you mean with a 'silent' timer?

BR,

Wim.

I would like not to have anything in the log on timer timeout, because if I set timer's interval to 10ms, the log very quickly fills with requests info from a timer.

But I now I think that it's impossible, because when application state changes (timer event) it should send that info to the browser.

Since they're actual requests, they show up in the logs. At the place where the access log is writtten, the server just sees the request, and it doesn't know if it's a timer request, if it's associated with a session, ... Can I suggest to use Wt's server push infrastructure instead? That will generate much less events, especially when used in combination with websockets. It feels a bit awkward to have a webapplication that generates 100 requests per second per session...

BR,

Wim.

What does it mean "Wt's server push infrastructure"? WServer::post?

I need so high timer frequency to smoothly draw an animated widget.

See documentation of WApplication::enableUpdates()

Enabling websockets is also recommended (in wt_config.xml).

BR,

Wim.

Wim Dumon wrote:

See documentation of WApplication::enableUpdates()

I've tried it. But after app->triggerUpdate() I get the same series of requests in the log, as if I used WTimer events.