[jdev] Changing delivery presence
jabber.org at ralphm.ik.nu
Tue Apr 12 08:35:15 CDT 2005
On Tue, Apr 12, 2005 at 06:51:16AM +0200, Tijl Houtbeckers wrote:
> On Tue, 12 Apr 2005 05:57:45 +0200, Leonardo Galicia Jiménez
> <valkyreii at hotmail.com> wrote:
> >My question is, there is a way that i can do this or somenthing similar
> >without affect the code jabber server?. There is a way for publishing
> >information, process it with some entity and after that disclose it?
> >I really will appreciate any suggestion.
> You should do this with a modified PubSub server. Take a look at Section
> "8.1.2 Create a New Node" of JEP-0060. In particular look at the
> <configure/> node. In section "8.2.1 Configure a Node" it is explained how
> you can use it. It probably doesn't quite suit you just yet.
> However, then look up just a bit in section 8.2. It states:
> "Implementations SHOULD use the Data Forms protocol to allow the node
> owner to accomplish the configuration". A long while ago by now, it took
> me a long discussion with some of the people involved in making this JEP
> to change that into the SHOULD it is today from the MUST it used to be.
> I'm glad to see a real use case for what I was thinking of at the time. I
> still think MAY is better than SHOULD, but it should work now too.
Yes, I was a proponent of this as well, in that discussion. However, it
seems the JEP-0060 schema doesn't allow other namespaces then x:data. This
is probably an error, and I'll take this up with the (other) authors.
> What this means is that now, you can use ANY XML format to configure your
> node. In this case, GeoPriv XML. As you can see, modifying a PubSub can be
> done in a protocol compliant way, by making a Geopriv JEP. You can also
> make it work for everyone by running just one modified pubsub server.
I'm not sure about other implementations, but I specifically designed Idavoll,
my pubsub service implementation, to allow other business rules, depending
on the target application. Maybe you could use it as a start for building out
your application. See http://idavoll.jabberstudio.org/ or contact me privately
via Jabber (prefered! JID: ralphm at ik.nu) or E-mail.
> Since you might want to send "normal" configuration data as well (eg
> access control) I think JEP-0060 should better show that it's possible to
> have two or more <configure/> nodes during creation. Also, to be sure I'd
> take a look at the schema of the JEP to see if it is properly in line with
> what the JEP allows as I've described.
This is not needed. You can have more than one child in <configure/>.
More information about the JDev