All times are UTC.
00:27:48 <-- EionRobb1 has quit (Connection closed) 00:28:08 --> EionRobb has joined #instantbird 01:27:11 --> micahg has joined #instantbird 01:52:30 <-- EionRobb has quit (Connection closed) 01:54:16 --> EionRobb has joined #instantbird 02:43:36 <-- unghost has quit (A TLS packet with unexpected length was received.) 03:09:16 <instant-buildbot> build #1540 of linux-nightly-default is complete: Failure [4failed compile] Build details are at http://buildbot.instantbird.org/builders/linux-nightly-default/builds/1540 03:51:05 <instant-buildbot> build #1763 of win32-nightly-default is complete: Success [3build successful] Build details are at http://buildbot.instantbird.org/builders/win32-nightly-default/builds/1763 03:57:03 <instant-buildbot> build #2925 of macosx-nightly-default is complete: Success [3build successful] Build details are at http://buildbot.instantbird.org/builders/macosx-nightly-default/builds/2925 04:34:03 <-- hadi has quit (Quit: Instantbird 1.6a1pre -- http://www.instantbird.com) 05:04:20 --> afiksof has joined #instantbird 05:40:22 <-- nhnt11 has quit (Ping timeout: 121 seconds) 06:02:28 <-- afiksof has quit (Connection closed) 06:10:36 --> nhnt11 has joined #instantbird 06:10:37 * ChanServ sets mode +h nhnt11 06:16:36 <instant-buildbot> build #450 of linux64-nightly-default is complete: Failure [4failed compile] Build details are at http://buildbot.instantbird.org/builders/linux64-nightly-default/builds/450 06:20:35 --> afiksof has joined #instantbird 06:24:38 <-- afiksof has quit (Ping timeout: 121 seconds) 06:58:06 <-- nhnt11 has quit (Quit: Instantbird 1.6a1pre -- http://www.instantbird.com) 06:58:10 --> nhnt11 has joined #instantbird 06:58:11 * ChanServ sets mode +h nhnt11 07:04:18 <-- nhnt11 has quit (Ping timeout: 121 seconds) 07:17:36 <-- Tonnes has quit (Connection closed) 07:23:14 --> mpmc has joined #instantbird 07:31:02 --> Tonnes has joined #instantbird 08:16:21 --> gerard-majax has joined #instantbird 08:31:30 --> Bollebib has joined #instantbird 08:46:03 <-- gerard-majax has quit (Ping timeout: 121 seconds) 08:48:12 --> gerard-majax has joined #instantbird 09:03:17 <-- gerard-majax has quit (Ping timeout: 121 seconds) 09:20:32 --> nhnt11 has joined #instantbird 09:20:33 * ChanServ sets mode +h nhnt11 09:50:20 --> aleth has joined #instantbird 09:50:21 * ChanServ sets mode +o aleth 09:53:43 <-- pWnnn has quit (Client exited) 09:53:49 <-- nhnt11 has quit (Quit: Instantbird 1.6a1pre -- http://www.instantbird.com) 10:23:59 <-- EionRobb has quit (Quit: Leaving.) 10:32:00 <-- freaktechnik has quit (Ping timeout: 121 seconds) 10:33:15 --> freaktechnik has joined #instantbird 10:56:33 --> gerard-majax has joined #instantbird 11:12:17 --> afiksof has joined #instantbird 11:22:09 --> pWnnn has joined #instantbird 11:27:05 --> gerard-majax_ has joined #instantbird 11:27:05 <-- gerard-majax has quit (Connection closed) 11:38:19 --> lissyx__ has joined #instantbird 11:38:23 <-- gerard-majax_ has quit (Ping timeout: 121 seconds) 11:38:26 * lissyx__ is now known as gerard-majax 11:50:42 --> nhnt11 has joined #instantbird 11:50:42 * ChanServ sets mode +h nhnt11 12:40:49 --> clokep has joined #instantbird 12:40:49 * ChanServ sets mode +o clokep 12:58:33 <-- gerard-majax has quit (Ping timeout: 121 seconds) 13:04:00 --> hadi has joined #instantbird 13:05:29 <-- pWnnn has quit (Client exited) 13:24:15 <-- nhnt11 has quit (Ping timeout: 121 seconds) 13:40:55 --> hadi1 has joined #instantbird 13:42:31 <-- hadi has quit (Ping timeout: 121 seconds) 13:42:32 * hadi1 is now known as hadi 14:51:25 <-- afiksof has quit (Quit: Instantbird 1.6a1pre -- http://www.instantbird.com) 14:52:04 --> afiksof has joined #instantbird 15:05:51 <-- mpmc has quit (Quit: Instantbird 1.6a1pre -- http://www.instantbird.com) 15:10:22 <-- clokep has quit (Quit: Instantbird 1.6a1pre -- http://www.instantbird.com) 15:10:35 --> clokep has joined #instantbird 15:10:35 * ChanServ sets mode +o clokep 15:26:53 --> nhnt11 has joined #instantbird 15:26:54 * ChanServ sets mode +h nhnt11 16:39:37 --> Mnyromyr has joined #instantbird 16:40:04 --> pWnnn has joined #instantbird 16:54:39 --> abdelrhman has joined #instantbird 17:11:41 --> gerard-majax has joined #instantbird 17:24:25 <-- gerard-majax has quit (Ping timeout: 121 seconds) 18:32:52 <-- Mnyromyr has quit (Quit: ChatZilla 0.9.92 [SeaMonkey 2.38/20150923193515]) 18:34:05 <-- nhnt11 has quit (Ping timeout: 121 seconds) 18:52:40 --> mpmc has joined #instantbird 19:18:15 <-- pWnnn has quit (Client exited) 19:24:08 --> mib_uuwk1y has joined #instantbird 19:25:28 <-- mib_uuwk1y has quit (Quit: http://www.mibbit.com ajax IRC Client) 19:30:21 --> EionRobb has joined #instantbird 19:33:15 <-- clokep has quit (Ping timeout: 121 seconds) 19:33:25 --> clokep has joined #instantbird 19:33:26 * ChanServ sets mode +o clokep 19:38:51 <-- aleth has quit (Ping timeout: 121 seconds) 19:41:31 <-- clokep has quit (Ping timeout: 121 seconds) 19:56:40 --> aleth has joined #instantbird 19:56:41 * ChanServ sets mode +o aleth 20:13:16 --> nhnt11 has joined #instantbird 20:13:16 * ChanServ sets mode +h nhnt11 20:52:49 --> pWnnn has joined #instantbird 20:54:37 <-- pWnnn has left #instantbird () 21:32:24 <-- hadi has quit (Connection closed) 21:32:32 --> hadi has joined #instantbird 21:36:18 --> gerard-majax has joined #instantbird 21:49:22 --> pWnnn has joined #instantbird 22:08:20 <-- mpmc has quit (Quit: Instantbird 1.6a1pre -- http://www.instantbird.com) 22:11:09 <abdelrhman> aleth: I want to check if we support setInterval in jsm? 22:11:54 <aleth> yes 22:12:21 <abdelrhman> where can I define it? 22:13:12 <aleth> https://developer.mozilla.org/en-US/docs/Mozilla/JavaScript_code_modules/Timer.jsm 22:15:01 <abdelrhman> Thanks ;). Currently, I'm working on queuing vcard requests 22:15:16 <aleth> Do you need an interval for that? 22:15:54 <aleth> You could just send the next request when the response to the previous one arrives 22:16:37 <abdelrhman> I'm sending 10 requests for each interval 22:18:01 <aleth> Isn't that more complicated? You have to check whether all 10 responses have arrived anyway before sending more 22:18:24 <-- gerard-majax has quit (Ping timeout: 121 seconds) 22:20:43 <aleth> "You could just send the next request" or the next 5 or 10 or whatever, of course 22:20:49 <abdelrhman> I do not check if there is a response, I just avoid sending a lot of vcard requests in short time 22:21:31 <abdelrhman> by setting the interval and each call send 10 requests in the queue of jids 22:21:46 <aleth> The problem is you don't know what the server considers a short time... 22:22:22 <aleth> The idea with waiting on responses is that if the server decides to throttle the responses, you can react. 22:26:42 --> flo-retina has joined #instantbird 22:26:43 * ChanServ sets mode +qo flo-retina flo-retina 22:26:44 <abdelrhman> Ah, so we can trigger the next request when server's response arrives 22:26:48 <aleth> Right. 22:27:05 <abdelrhman> OK 22:27:20 <aleth> As an example, some IRC servers will throttle (slow down dramatically) the rate at which they respond to commands if you send too many too quickly. 22:27:34 <aleth> But "too many" and "too quickly" are configurable, server-side. 22:35:32 <abdelrhman> yes, you are right and we do not know how they configure that, so we assume the worst case 22:43:55 <aleth> abdelrhman: do servers have to respond to vcard requests (at least with an error) or can they just time out? 22:46:15 <abdelrhman> yes, it must respond 22:46:18 <abdelrhman> "If no vCard exists, the server MUST return a stanza error (which SHOULD be <item-not-found/>) or an IQ-result containing an empty <vCard/> element." 22:46:29 <abdelrhman> XEP-0054 22:46:36 <aleth> good, that simplifies things ;) 22:46:39 <EionRobb> that doesn't say how quickly a response should return though 22:50:35 <abdelrhman> yes, but this will help us trigger next vcard request 22:51:11 <EionRobb> yeah, but your assumption is that you get a response 22:59:43 <abdelrhman> Do you mean we may not get a response due to any kind of failure between client and server (e.g. packet loss, etc.) 23:01:55 <EionRobb> no, if it times out fetching the vcard from the server (I've seen this happen on crappy servers) 23:02:15 <EionRobb> it'll still fetch the vcard, but it can take a long time to do so 23:15:08 <abdelrhman> but, how time should be used for time out (the maximum)? 23:21:07 <-- Bollebib has quit (Ping timeout: 121 seconds) 23:26:18 <abdelrhman> I think this is the problem of these "crappy" servers that they are slow in responses. We can not do anything for getting responses faster. 23:29:46 <EionRobb> yeah, but its just something to watch out for in the stuff you're doing (i.e. don't expect the server to respond within X seconds) 23:35:06 <abdelrhman> OK, we use callbacks to handle that and I think that would be sufficient. 23:59:35 <-- abdelrhman has quit (Ping timeout: 121 seconds)