Would you please declare me about the criteria of dividing modules into boot, core and standard? The concept about differend kind of modules would do good to understand the mechanism for me. Thank you very much.
Another four questions:
Is it possible to save the message history on the server like muc history?
How to deal with blocking communication?
Is it a good idea to save the file on the server while transfering file between two users?
Is there a framework to implement the gateway model described in the RFC 3920?
dividing modules into boot, core and standard? The
concept about differend kind of modules would do good
to understand the mechanism for me. Thank you very
much.
Actually, that code is a bit old and needs to be rewritten. However, boot modules are the ones that are needed for setup to work if I remember correctly.
Another four questions:
Is it possible to save the message history on the
server like muc history?
Yes, you can enable message auditing, which saves all messages to a file.
How to deal with blocking communication?
What do you mean? Jive Messenger doesn’‘t support NIO yet, but we’'d like to in the future.
Is it a good idea to save the file on the server
while transfering file between two users?
If Jive Messenger becomes a SOCKS gateway, it may need to save parts of files during transfer.
Is there a framework to implement the gateway
model described in the RFC 3920?
There’‘s no framework yet, but we’'d love to have one!