Project

General

Profile

Actions

Bug #3549

closed

Progressive Bootstrap Causes High Number of Application Instances

Added by Josh Lampco about 10 years ago. Updated about 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
08/27/2014
Due date:
% Done:

0%

Estimated time:

Description

The problem can be recreated using the simple modified hello world program. The issue I am experiencing is the number of times my createApplication(...) function is being called. When progressive bootstrap is enabled, the amount of times is around 40. When the progressive bootstrap is disabled everything seems to work correctly. In my application, I am setting the internal path to "/" with setInternalPath("/", true); When I DO NOT set the internal path to "/", I still get multiple calls to createApplication(...) but not as many - around 4.

Environment Information

Test program is run using the following command:

--approot=. --docroot='.;/resources, /favicon.ico' --http-address=0.0.0.0 --http-port=80

This is running in Ubuntu 12.04

Library Version Wt.3.3.3


Files

wt_config.xml (22.6 KB) wt_config.xml Current Config File Josh Lampco, 08/27/2014 08:50 PM
testing-progressive-bootstrap.cpp (712 Bytes) testing-progressive-bootstrap.cpp Simple Modified Hello World Program Josh Lampco, 08/27/2014 08:50 PM
Actions #1

Updated by Koen Deforche about 10 years ago

  • Status changed from New to Feedback

Hey Josh,

Can you see for which 'GET's you see new instances? I suspect it's because some browser requests for static files still end up in Wt.

--approot=. --docroot='.;/resources, /favicon.ico' --http-address=0.0.0.0 --http-port=80

should be:

--approot=. --docroot='.;/resources,/favicon.ico' --http-address=0.0.0.0 --http-port=80

Regards,

koen

Actions #2

Updated by Josh Lampco about 10 years ago

Koen,

This indeed seems to be the case. Apparently, Chrome asks multiple times for the favicon.

Thanks!

Actions #3

Updated by Koen Deforche about 10 years ago

  • Status changed from Feedback to Resolved
Actions #4

Updated by Koen Deforche about 10 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF