Opened 15 years ago
Closed 14 years ago
#1147 closed enhancement (fixed)
MaestroAPI: Make MaestroAPI threadsafe
| Reported by: | ksgeograf | Owned by: | jng |
|---|---|---|---|
| Priority: | low | Milestone: | Maestro-3.0 |
| Component: | Maestro | Version: | |
| Severity: | trivial | Keywords: | MaestroAPI threadsafe |
| Cc: | External ID: |
Description
The MaestroAPI uses a single WebClient for all communication. This should be changed to using HttpWebRequest and HttpWebRespone as they are more effictient, and would open up for a multithread capable library.
There are only a few caches in MaestroAPI that needs to be protected by locks. Other than that it should be a breeze to fix this.
Change History (3)
comment:1 by , 15 years ago
| Milestone: | → Maestro-2.1 |
|---|---|
| Status: | new → assigned |
comment:2 by , 15 years ago
| Milestone: | Maestro-2.1 → Maestro-2.5 |
|---|---|
| Owner: | changed from to |
| Status: | assigned → new |
comment:3 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Marking as fixed in 3.0 sandbox as we now use HttpWebRequest/HttpWebResponse pairs instead of WebClient.
All known shared state in HttpServerConnection are protected by locks.