| Commit message (Collapse) | Author | Files | Lines |
|---|
|
to certain other groups.
It doesn't let them know, though the last group added will be their
active group. This replaces a PHP script I used to use, that got broken
by a PHP update. It also didn't let people know, no one complained.
This is better.
Another attempt at sorting out the auto group chicken and egg problems.
Are you a local? Asking for a friend.
Hypergridders have their full name in firstname, and their grid in
lastname. Sometimes.
Code filled with gotos may be spaghetti code, but object oriented code
can be like chopped spaghetti that's hidden all over the kitchen. At
least with gotos you can follow them.
|
|
Are you a local? Asking for a friend.
|
|
|
|
|
|
|
|
to print various counts of capability invocation by user and by cap
This currently prints caps requests received and handled, so that overload of received compared to handled or deadlock can be detected.
This involves making BaseStreamHandler and BaseOutputStream record the ints, which means inheritors should subclass ProcessRequest() instead of Handle()
However, existing inheriting classes overriding Handle() will still work, albeit without stats recording.
"show caps" becomes "show caps list" to disambiguate between show caps commands
|
|
of OSHttpRequest/OSHttpResponse.
This is required for the substitution of different HTTP servers or the newer HttpServer.dll without having to commit to a particular implementation.
This is also required to write regression tests that involve the HTTP layer.
If you need to recompile, all you need to do is replace OSHttpRequest/OSHttpResponse references with IOSHttpRequest/IOSHttpResponse.
|
|
authorization service rather than from the account.
This is to accomodate situations where the authorization service is being used by the hypergrid, where visitors have no user account.
See http://opensimulator.org/mantis/view.php?id=5517, this code is somewhat adapted/cleaned up from Michelle's patch
I'm a little ambivalent about this since visitors could put anything in firstname/lastname so it's not much of an auth measure.
It's up to the auth service to decide which data it actually uses.
Possibly we should be passing through other info such as agent circuit ip
|
|
Make all current modules support the configuration name option
|
|
Make all current modules support the configuration name option
|
|
|
|
and can be displayed at the client when an avatar is denied access to a region
|
|
|
|
Authorization messages over http. Added handling code for these in the AuthorizationServerConnector and AuthorizationServicesConnector
|
|
|
|
always grant access to an avatar entering the region if requested.
|
