Not logged in. · Lost password · Register
Forum: agsXMPP RSS
Receiving own messages from another resource
Avatar
Aleppo 2010-03-17, 12:01 #1
Member since Mar 2010 · 2 posts
Group memberships: Members
Show profile · Link to this post
Subject: Receiving own messages from another resource
Hi,

I'm trying to create message archiving functionality to existing system. The idea would be to have a separate web server that collects and archives the message history. I can already archive all the messages that are coming from the other participant, but receiving messages from own main resource seems to be impossible for me to accomplish.

Ex:Romeo                                                       Ex:Julia
   romeo@server/main                                          julia@server/main
   romeo@server/archiver                    


So, the situation is that the archiver can easily receive all the messages coming from Julia, but it cannot receive any messages that are sent from Romeo/main. So, now I'm actually asking the different possibilities for doing this? I'm unable to chage the code of the 'main' -resource, although I might be able to change some of the settings from the XMPP server.

Or are there any other methods that I could use to receive the messages also from 'main' at the archiver resource?
Avatar
Alex 2010-03-17, 18:41 #2
Member since Feb 2003 · 4449 posts · Location: Germany
Group memberships: Administrators, Members
Show profile · Link to this post
if you don't send a copy of the messages to the archiver this will not work. Because you say you are unable to change the code of the client this will not work.

I would look on the server side. There are many servers which have good archiving features or plugins. The best solution is to archive the messages on the server with no additional overhead.
Avatar
Aleppo 2010-03-18, 10:55 #3
Member since Mar 2010 · 2 posts
Group memberships: Members
Show profile · Link to this post
Thanks, I suspected this as well, although I hoped that XMPP protocol would have offered me an easy way out because it's initially designed to be shared among multiple resources. The reason that I'm building a separate archiver tool is exactly because I cannot access the code of the original main client. (Otherwise I would build the archiving functionality there)

But thanks for the info, this prevents me from banging my head against the wall. I'm starting to look for other solutions for my problem.
Avatar
Alex 2010-03-18, 11:09 #4
Member since Feb 2003 · 4449 posts · Location: Germany
Group memberships: Administrators, Members
Show profile · Link to this post
look for the solution on the server side.

Its also up to the server how to handle messages when there are multiple resources online. Some servers deliver the message to each online resource. So you could login a archiving client under a special resource for each user. But IMHO this is a hack and no real solution when you can archive messages on the server with nearly no additional overhead,

Alex
Close Smaller – Larger + Reply to this post:
Verification code: VeriCode Please enter the word from the image into the text field below. (Type the letters only, lower case is okay.)
Smileys: :-) ;-) :-D :-p :blush: :cool: :rolleyes: :huh: :-/ <_< :-( :'( :#: :scared: 8-( :nuts: :-O
Special characters:

Forum: agsXMPP RSS