Dear developers,
today the first OpenSpime library has been launched! It is written in Python language and can be downloaded from it’s project page on Google Code. This version 0.1 does not fully support the OpenSpime protocol v0.9 yet, however it currently already supports:
See what OpenSpime can already do! You may try PyOpenSpime directly under your My Developer page, where you’ll be able to get the necessary resources to run it in a few minutes. To get you started, I suggest you follow the tutorial that has been written by Davide “folletto” Casali.
PyOpenSpime is released under the GNU General Public License v3.
You must be logged in to post a comment.
Hej, could you elaborate a little on the current state of the other nodes within the OpenSpime architecture? Is any work done providing a SpimeGate?
hi goern,
as you correctly have understood spimes and scopenodes can be both created with the help of pyopenspime.
as far as spimegates, we currently only use ejabberd as xmpp server, coupled with a small service which provides certification functionalities [at the address services@developer.openspime.com/cert]. a very basic SpimeGate is nothing more than a XMPP server, so you may implement one yourself using one of the available XMPP servers out there.
remember that the definition of OSID is of an OpenSpime IDentifier, which is nothing more than JID with some characteristics, all defined in the architecture documentation that you can find on openspime.org.
moreover, right now you can have two OSID for free using the OpenSpime Developer Network spimegate which is available to all subscribed developers.
hopefully this clears it up for you.
:)
cheers,
r.
Cool! I was wondering the same thing as goern - it would be confidence building to have the configuration for a spimegate downloadable somewhere, but in any case, thanks for providing some pointers.
Saw one odd thing in the debug output:
DEBUG:MyScopeNode:get content of node
DEBUG:MySpime:adding node ‘content-type’ encrypted attribute
Compare the spelling of ‘transport’ versus ‘tranport’. I assume this is a typo.
Silly me. Let’s try it with those characters encoded:
DEBUG:MyScopeNode:get content of <transport/> node
DEBUG:MySpime:adding <tranport/> node ‘content-type’ encrypted attribute
yes natch,
definitely a typo :) this has been corrected in pyopenspime svn. may i suggest you use the tracking system http://code.google.com/p/pyopenspime/issues/list to report such issues? it’ll be easier to follow them up.
natch, a basic spimegate has no particular settings, just a normal xmpp server will do :)
cheers,
r.