For my implementation of IRC support, I am looking for a way to
server message. Specifically those messages that inform the user or
communicate to a user without being related to chatroom. For
the server notices, message of the day, user mode changes, etc.
I wanted to use the so called "system chatroom" for these message,
however this chatroom seems to be unavailable during the
of the server connection. Only after the connection has successfully
completed and the ProtocolProviderService is "REGISTERED" can I
access/create this system room.
* I am supposed to use a system chatroom for this purpose? (If
is it intended for then?)
Yes, that's what it is intended for.
* What do you suggest I could use in order to show the user these
message, for example to inform the user of messages sent to the user
while the connection is being established? (It doesn't feel like the
logging window is the right tool for this job ...)
Once you connect you should deliver everything through the system
room. We are not using that for XMPP so feel free to modify its
behaviour as it best fits your IRC implementation!
That's handy. It would be nice if we can open a chatroom prior to
actually having connected, since connections could also fail somewhere
during the "initiation rite" and we might still be interested in what
the server did communicate.
Well ... that's normally the stuff that you'd see in error dialogs.
I am not sure I see what you mean though. If you can't setup your socket to the server then it can't tell you anything to show in a sys room. If you do establish your TCP connection then, as far as IRC is concerned, you can consider yourself "registered" from a Jitsi perspective.
We would not be fully connected yet, though.
Could you please describe a bit more the state that you consider as "not fully connected" ? What registration state do you see Jitsi attributing to this?
I am thinking of exploring a few possiblities in that area, as far as
time permits and my wishes don't go against the Jitsi framework. (Prior
to a fully established connection, the communication in the chatroom
would be one-way though.)
Note that I plan to not show these messages by default, since
them are not useful if you know that a connection has been
repeatedly without any problems. It can be useful in case of
I believe Hristo will soon be working on a way to indicate whether a
message should be used to trigger a chat window to open (e.g. we'd
like auto-connect chat room to not show by default. only when
there's something worth showing). I think we should consider the
system chatroom there as well.
I am not familiar with the idea.
Aren't we doing something similar already with normal conversation
We should be but no. We just popup windows as soon as anything arrives.
System messages being just a notification that has less
emphasis already. We can consider the system room as just another "chat
partner" in that sense.
Right. And we should make sure that most of the stuff that we get from this partner is tagged as non-critical. Unless, for example, if it's output that we are getting in result of some user command.
If you'd want to see the server notices and MOTD, add them as
conversation message, otherwise add them as system messages. Or
something like that ...
Would these messages be visible afterwards or would they just be lost?
You mean: will they be saved in history? Those for the regular chats will be, yes. We should probably make sure that those in the system chat room have some sort of a tag that tell the history service not to bother though.
On 06.12.13, 09:46, Danny van Heumen wrote:
On Fri, Dec 6, 2013 at 1:21 AM, Emil Ivov <email@example.com > <mailto:firstname.lastname@example.org>> wrote:
On 05.12.13, 17:22, Danny van Heumen wrote: