Project

General

Profile

Actions
Copy link

Bug #374

closed

WResource not parallel

Added by Anonymous almost 14 years ago. Updated over 13 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Koen Deforche
Target version:
-
Start date:
05/25/2010
Due date:
% Done:

0%

Estimated time:

Description

The doc states that :

"Unlike event notifications to a Wt application, resource requests are not serialized, but are handled concurrently"

However a scoped_lock object is created a the beginning of

WResource::handle(WebRequest *webRequest, WebResponse *webResponse, Http::ResponseContinuation *continuation),

serializing concurrent call to a WResource.

Marc

Actions
Copy link
 #1

Updated by Koen Deforche almost 14 years ago

  • Status changed from New to Resolved
  • Assignee set to Koen Deforche

Hey Marc,

The second lock grabs only a mutex protecting the single resource (from being deleted while being handled): the mutex is specific to a single resource. The application allows concurrent access to different resources, and in parallel with event notifications. I think the documentation should be updated to make that clear.

You can for example see how this concurrent access improves performance in the mandlebrot example, where the server is computing and serving the tiles in parallel.

Regards,

koen

Actions
Copy link
 #2

Updated by Pieter Libin over 13 years ago

  • Status changed from Resolved to Closed
Actions
Copy link

Also available in: Atom PDF