| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
to the client thread crashing if uncaught.
|
| |
|
|
|
| |
Mantis #3225.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
results in a memory leak which will make the region crash and burn
after a while.
|
| |
|
|
|
|
|
|
|
|
| |
* commented out [Obsolete(....)] attributes where no replacement feature
was available: if we want to attribute code that we think needs to be
reworked, we should define a new attribute and use that instead
(together with a little tool to retrieve all the attributed code then)
* commenting out unused variables
|
| |
|
|
| |
currently not actually used
|
| |
|
|
|
| |
Fix spelling typo (Thanks ChrisDown for pointing this out)
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
the status of the region using the region http uri just passed in
* If the status cannot be retrieved, then the region startup will terminate.
* The aim of this is for earlier detection of situations where the region can send messages out but cannot accept incoming requests (often due to firewall issues)
* This is currently an extremely simplistic check which completely trusts whatever http uri is given by the region
* This contact may be problematic, though since the user service needs to be able to contact the region http uri, it doesn't seem unreasonable for the grid to have to be able to do so too at this stage
* This change will require a prebuild
|
| | |
|
| |
|
|
|
| |
* Made a bunch more members static, removed some dead code, general cleaning.
|
|
|
with namespaces.
|
