[Opensim-dev] Existing CAPs

[Mikko Pallari]

It seems that this was PublicSnapshotDataInfo was introduced in revision 4735. It was to "enhance search capability on OpenSim sims using external search engines such as Metaversink.com and others."

Cheers,
Mikko

From: opensim-dev-bounces at lists.berlios.de [mailto:opensim-dev-bounces at lists.berlios.de] On Behalf Of Diva Canto
Sent: 2. maaliskuuta 2009 3:53
To: opensim-dev at lists.berlios.de
Subject: Re: [Opensim-dev] Existing CAPs

I found this page:
http://wiki.secondlife.com/wiki/Current_Sim_Capabilities

Which, not surprisingly, is not entirely in sync with what we have in the code. ObjectAdd is not there, and there are many on that list that we don't have.
But the PublicSnapshotDataInfo is still a mystery.


MW wrote:
I don't know about the snapshot one because I haven't actually looked to see what CAPS the client is requesting lately. But the others are caps services that the client requests (or at least used to).

As you know when the client first connects it makes a request to the caps seed that it was passed during the xml-rpc login request.

This is handled in Caps.cs class in:  public string CapsRequest(string request, string path, string param,  OSHttpRequest httpRequest, OSHttpResponse httpResponse). If in that method you add a m_log.Info(request); you can actually see the list of CAPS services it is interested.

So I guess the SL docs are missing a lot of messages.


But anyway our CAPS support is really in need of a good rewrite.


--- On Mon, 2/3/09, Diva Canto <diva at metaverseink.com><mailto:diva at metaverseink.com> wrote:
From: Diva Canto <diva at metaverseink.com><mailto:diva at metaverseink.com>
Subject: [Opensim-dev] Existing CAPs
To: opensim-dev at lists.berlios.de<mailto:opensim-dev at lists.berlios.de>
Date: Monday, 2 March, 2009, 1:27 AM

I'm trying to understand what exactly *we* are doing wrt CAPs. I'm a bit



confused.

Here's the list of all capabilities I see in the code:



EventQueueGet   http://<sim>/CAPS/EQG/<random uuid>

ObjectAdd   http://<sim>/CAPS/OA/<random uuid>

RemoteParcelRequest   http://<sim>/CAPS/<caps seed>0009/

MapLayer   http://<sim>/CAPS/<caps seed>0001/

PublicSnapshotDataInfo   http://<sim>/CAPS/<caps seed>DS0001/

ParcelVoiceInfoRequest   http://<sim>/CAPS/<caps seed>0007/

ProvisionVoiceAccountRequest   http://<sim>/CAPS/<caps seed>0008/

ViewerStats

 http://<sim>/CAPS/VS/<random uuid>

NewFileAgentInventory   http://<sim>/CAPS/<caps seed>0002/

UpdateNotecardAgentInventory   http://<sim>/CAPS/<caps seed>0004/

UpdateScriptAgentInventory   <same as above>

UpdateScriptAgent   <same as above>

UpdateScriptTaskInventory   http://<sim>/CAPS/<caps seed>0005/

UpdateScriptTask   <same as above>



I've cross-referenced these with LL messages documented here

http://wiki.secondlife.com/w/index.php?title=Category:Messages

And I found only 2 names that match, namely: ObjectAdd and ViewerStats.



Can someone please explain to me where the names of these capabilities

come from? These are the names that are being sent to the viewer, so

they must have a meaning there.

I'm intrigued about them all, because there are so few matches with the

LL message list, but particularly about the PublicSnapshotDataInfo



capability, since I was the original developer of that module. As far as

I know, the viewer knows nothing about the data snapshot feature -- why

are we sending it that capability?



<Totally confused>

Crista

Thanks.

_______________________________________________

Opensim-dev mailing list

Opensim-dev at lists.berlios.de<mailto:Opensim-dev at lists.berlios.de>

https://lists.berlios.de/mailman/listinfo/opensim-dev











________________________________






_______________________________________________

Opensim-dev mailing list

Opensim-dev at lists.berlios.de<mailto:Opensim-dev at lists.berlios.de>

https://lists.berlios.de/mailman/listinfo/opensim-dev



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://opensimulator.org/pipermail/opensim-dev/attachments/20090302/ebf521b5/attachment-0001.html>