Hi,
If I understand well, your idea is about building a system where people will be able to exchange messages through a mix of chat client + wiki + RSS / ATOM. This seems somewhat similar to building a forum where you would add replies through an XMPP interface rather than through a web one. It would have the following steps:
1. Create a new discussion on the wiki 2. Send messages to that discussion through Jabber 3. Be notified of new messages via RSS
Ad. 3 I would rather said that user will be notified by something like RSS. This something is part of XMPP. It makes this solution real-time one. Notifications are not standard messages, client should rather display it as a change in subscribed node.
This looks complex to me. 2 remarks:
- The initial proposal aims at addressing 2 needs: - *Storing content from chat discussions in the wiki to archive them and make them searchable*. The aim is to not get in the way of chat users but rather provide them with a public searchable archive. This is an important part of the project and does not seem to be addressed by your proposal.
I don't know did you look into my application but I already proposed some store mechanism so bind it with search engine shouldn't be very difficult but rather a obvious issue. - *Letting users chat right into the wiki. *This means letting people
exchange messages together while working on a page for instance. The use case described here is for real-time communication while your proposal is not.
As I said my proposal is not real chat but it is real-time. I mentioned disadvantages of chat logging in my last mail. Thank you for your advices and review. I would rather change my proposal and describe other solution instead change picked up idea. IMs are my branch so I would like to work with them, I am also keen on cross technologies services ... so this idea is created for me. I saw that some other student is working on this case but GSoC is a competition. Jan J. Roman