On Oct 31, 2007 11:18 AM, Paulo Sergio <[EMAIL PROTECTED]> wrote: > Hi all,
hi Paulo good to hear from you again just FYI IDLE has come up in the the MailboxAPI design threads currently running. feel free to jump into that thread if you have any comments or ideas. > i have some questions about IMAP IDLE command. I'm working with James > (connecting it to a web service backend, both authentication and data), > and i reach the point where i really need IDLE command, the problem is that > in my case, the server (james ) will be externally notified when something > new is in mailbox, the server that will notify for changes has access to the > complete user information. My current problem is that when the notification > reaches James server i would need to know what is the user that has new > data, the problem here is that i would need access to the opened sessions, > is this possible? not sure... > it would work like this: > > client sends login to james-> james validates login in the webservice -> > webservice reuturns a valid session id (witch is stored as an attribute of > the user session) > cllient sends IDLE to james server -> james server sends Idle to the > webservice (at this point the webservice inserts this user as a > "notifiable", ) > when something new is detected, a connection will be opened to james server > and the information about the sessionid is sent , at this point james server > knows that the user witch a specified ssid needs to fecth information, the > problems here is that at this point i need the correspondent session to the > user with the received ssid. > My idea would be to add a special command to the james server to receive > notifications, this would be ok if in then i could have access to the user > session.. yeh - one of the limitations of the current MailboxAPI design is the muddle around mailbox sessions > so, is this possible ? depends on what you mean by that ;-) of course since JAMES is open source so you can probably just create a local fork if necessary given the current MailboxAPI then you may need to do something clever - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
