Hi there guys,
I am building a XMPP service around jabberd2 and I am very impressed
with the current architecture. However, as I am getting further into
our implementation, a couple of problems have become apparent.
Problems:
- We need to maintain per user session data in c2s. For example:
Great! Yes I was a bit iffy on the ³custom² approach myself given it
really didn¹t align with any authentication method. But if API
breakage is okay, this is definitely the cleanest way.
- Retrofit existing interfaces with the necessary data.
a. Introduce void *sess_private in sess_t.
It's
I have modified the
APIs to pass sess_t and then the implementation can choose to pack it
in their private authreg_private data if they so choose.
WFM :-)
Changes almost ready to go, will submit a pull request within the hour.
Changes almost ready to go, will submit a pull request within the hour.
Pull request submitted: https://github.com/jabberd2/jabberd2/pull/72
Issue create to track (perhaps excessive):
https://github.com/jabberd2/jabberd2/issues/71
Looking forward to comments and feedback!
Thanks,
Shawn
Hey there,
Turns out that when inserting items in xhash, the code stores a pointer to
the key passed in by the user in the xhash node and uses that later to
compare in _get. The problem is that it breaks scenarios where the user may
use a temp buffer to build the key, then insert or put it in the
Pull request #79 submitted.
https://github.com/jabberd2/jabberd2/pull/79
On 8/28/14, 10:51, Shawn Debnath sh...@debnath.net wrote:
Hey there,
Turns out that when inserting items in xhash, the code stores a pointer to
the key passed in by the user in the xhash node and uses that later
Could you rethink your design to include the identifier as a part of the
object it names?
Yep, looks like this is a cleaner way out.
On 5/26/15, 9:08 AM, Matěj Cepl mc...@cepl.eu wrote:
(a follow-up to the issue
https://github.com/loqui/im/issues/732#issuecomment-105519240)
I have a jabberd2 XMPP server on domain ceplovi.cz and I would
like to connect to it with Loqui. It works perfectly well with
pidgin, bitlbee,
Typically, the hyphen is a special character and the string containing it has
to be escaped correctly. Also evident from the way “object-sequence” or the
column names are escaped in the debug log. Have you tried running the query on
the database itself to check the results?
Googling for mysql
I agree with Tomasz that there are changes that are definitely needed
given how much technology has changed since jabberd2 was first released.
Re 1. Merging separate daemons to one.
I am not sure if merging them into one process is the best idea. It sure is
convenient, but isolation is a nice
10 matches
Mail list logo