From: Stas Z <sta...@gm...> - 2005-09-26 09:41:21
|
Hello I fixed the bug in the return value of a 'len' call to a message thread, it now returns 0 again when the thread is empty. It will be in the next release along with some other small fixes. I will release it this afternoon. I also added a new method called 'getUnreadMsg' which returns the inbox mes= sages marked 'unread'. I was wondering if we should change the way getMessagesbyFolder works. Perhaps we return only the unread messages when the inbox is chosen. The problem with calling getMess... with the 'inbox' is that on larger accounts you will get a "lockdown" due to the many calls to the Gmail servers. I think we also should limit the number of page call to avoid lockdowns. I would really like to hear any comments or ideas about this. Cheers, Stas -- A nation that continues year after year to spend more money on military def= ense than on programs of social uplift is approaching spiritual doom. Martin Luther King, Jr. |
From: Richard J. <jo...@gm...> - 2005-09-26 10:03:46
|
On 9/26/05, Stas Z <sta...@gm...> wrote: > Hello > > I fixed the bug in the return value of a 'len' call to a message > thread, it now returns > 0 again when the thread is empty. It will be in the next release along > with some other > small fixes. I will release it this afternoon. > Thanks for that, gmailfs users everywhere will thanks you (all 2 or 3 of them :-) ). > I also added a new method called 'getUnreadMsg' which returns the inbox m= essages > marked 'unread'. > > I was wondering if we should change the way getMessagesbyFolder works. > Perhaps we return only the unread messages when the inbox is chosen. > The problem with calling getMess... with the 'inbox' is that on larger > accounts you > will get a "lockdown" due to the many calls to the Gmail servers. > > I think we also should limit the number of page call to avoid lockdowns. > > I would really like to hear any comments or ideas about this. > I don't have a strong opinion on this, I dont use this call in gmailfs, however from an API point of view it might be better to add a getUnreadMessagesByFolder and have some kind of strategy of dealing with the lockdown issue. Can you only get the first page and then load the others on demand when the user tries to iterate over them? Regards, Richard. |
From: Stas Z <sta...@gm...> - 2005-09-26 11:29:59
|
On 9/26/05, Richard Jones <jo...@gm...> wrote: > Thanks for that, gmailfs users everywhere will thanks you (all 2 or 3 > of them :-) ). Are you sure, a quick look into the Debian popularity contest shows that they recorded 158 persons which installed it :-) And that only for Debian users who participate in the popularity contest. > > I also added a new method called 'getUnreadMsg' which returns the inbox= messages > > marked 'unread'. > > > I don't have a strong opinion on this, I dont use this call in > gmailfs, however from an API point of view it might be better to add > a getUnreadMessagesByFolder and have some kind of strategy of dealing > with the lockdown issue. That is probably better indeed, thanks. > Can you only get the first page and then > load the others on demand when the user tries to iterate over them? Perhaps, but it should also be possible when libgmail is run in some sort o= f automated process or from a script. Stas -- A nation that continues year after year to spend more money on military def= ense than on programs of social uplift is approaching spiritual doom. Martin Luther King, Jr. |
From: Stas Z <sta...@gm...> - 2005-09-26 11:33:06
|
On 9/26/05, Stas Z <sta...@gm...> wrote: > > > gmailfs, however from an API point of view it might be better to add > > a getUnreadMessagesByFolder and have some kind of strategy of dealing > > with the lockdown issue. > That is probably better indeed, thanks. Better, getUnreadMessagesByLabel. The only folder with unread messages would be the inbox. I assuming noone wants to read the spam folder :-) Stas -- A nation that continues year after year to spend more money on military def= ense than on programs of social uplift is approaching spiritual doom. Martin Luther King, Jr. |
From: Richard J. <jo...@gm...> - 2005-09-26 12:50:21
|
On 9/26/05, Stas Z <sta...@gm...> wrote: > On 9/26/05, Richard Jones <jo...@gm...> wrote: > > > Thanks for that, gmailfs users everywhere will thanks you (all 2 or 3 > > of them :-) ). > Are you sure, a quick look into the Debian popularity contest shows > that they recorded > 158 persons which installed it :-) > And that only for Debian users who participate in the popularity contest. > Interesting, I guess I judge by the number of complaints I get when Google changes something. Maybe seb is heading off most of those complaints :-) > > > I also added a new method called 'getUnreadMsg' which returns the inb= ox messages > > > marked 'unread'. > > > > > I don't have a strong opinion on this, I dont use this call in > > gmailfs, however from an API point of view it might be better to add > > a getUnreadMessagesByFolder and have some kind of strategy of dealing > > with the lockdown issue. > That is probably better indeed, thanks. > > > Can you only get the first page and then > > load the others on demand when the user tries to iterate over them? > Perhaps, but it should also be possible when libgmail is run in some sort= of > automated process or from a script. > By user I meant API user. This idea only really helps if they are doing work with the messages whilst iterating overthem otherwise they are still likely to get locked out. I guess the only real option here is to introduce artificial pauses if you detect the API user iterating too quickly (assuming that what is "too quickly" can be easily pre-determined). Regards, Richard. |