collab-uniba / econference4

Automatically exported from code.google.com/p/econference4
0 stars 0 forks source link

[xmpp, econference] Optimization checks to perfom upon event join #91

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Upon event joining by any participants, the system should do the following 
checks:
* Check that the moderator has already joined (i.e., # participants >= 2 and 
moderator is among them)

[optional and blocked by the aformentioned check]
* Check that current time is not before (<) the event schedule, unless current 
participants is the moderator. Other participants can join only iff time is >= 
schedule.
To lessen such constraint we can imagine that the moderator can join, say 15 
min. before the scheduled time, and any participant no earlier than 5 min. 
before the schedule.

Original issue reported on code.google.com by calefato.uniba@gmail.com on 27 Nov 2011 at 10:38

GoogleCodeExporter commented 9 years ago
* As a latecomer, upon joining history is received, and it's full of old chat 
composing messages that should be skipped.
An old chat composing notification will look like the following:

<message id="1nztN-18" to="econferencetest2@gmail.com/eConf.F471D0D0" 
from="room@conference.server.net/econferencetest2@gmail.com" type="groupchat">
  <composing xmlns="http://jabber.org/protocol/chatstates">
    <who>econferencetest2@gmail.com</who>
  </composing>
  <delay xmlns="urn:xmpp:delay"/>
  <x xmlns="jabber:x:delay" stamp="20111127T09:47:10"/>
</message>

Therefore we should skip composing message we they also contain a <delay /> 
tag. Adding an boolean isHistoryMessage() method looks ok.

Original comment by calefato.uniba@gmail.com on 27 Nov 2011 at 11:10

GoogleCodeExporter commented 9 years ago

Original comment by calefato.uniba@gmail.com on 17 May 2012 at 2:49