Thanks Tess,
It's the registration part that I'm hung up on. I grok the cap and the
polling part, but there are a bunch of LLHTTPRegistration entries for event
types that aren't in the list processed by
LLHTTPRegistrar::buildAllServices(), which confused me.
I thought that anything with an entr
The viewer requests for capabilities via the seed capability.
"EventQueueGet" is the capability for polling for events queues for
the client from the region. The viewer then periodically invokes that
capability essentially polling the server for messages. See
llviewerregion.cpp, lleventp
Infinity Linden wrote:
> lemme dig through my notes and see if i have more / better
> documentation on using caps.
>
> yes. if the viewer is still as i remember it, we have an event queue
> for the region you're connected to and for each adjacent region for
> object updates from child cameras. (
lemme dig through my notes and see if i have more / better documentation on
using caps.
yes. if the viewer is still as i remember it, we have an event queue for the
region you're connected to and for each adjacent region for object updates
from child cameras. (but... it's been close to a year since
I'm attempting to understand how the event queue in the viewer works,
specifically, creating and registering new services. I'm thankful for the
documentation in llhttpnode.h, but I'm still scratching my head a bit.
In LLHTTPRegistrar::buildAllServices(), I see all the message/* type nodes
getting
