Re: [Twisted-Python] imap4client.py example problem
On Wednesday 10 November 2004 14:10, Robert Penz wrote: after the talk in the channel I've following to add to the case. 1. it works if I just look for the mailbox "INBOX". thx krp for the tip. 2. the output of namespace() is [[['INBOX.', '.']], [], [['', '.']]] hope this info helps.
On Thu, 11 Nov 2004 08:26:25 +0100, "Robert Penz" <robert.penz@outertech.com> wrote:
On Wednesday 10 November 2004 14:10, Robert Penz wrote:
after the talk in the channel I've following to add to the case.
1. it works if I just look for the mailbox "INBOX". thx krp for the tip. 2. the output of namespace() is [[['INBOX.', '.']], [], [['', '.']]]
hope this info helps.
It sounds like both the server and Twisted are doing just the right thing. See rfc 2342 for an explanation of imap namespaces. Jp
It sounds like both the server and Twisted are doing just the right thing. See rfc 2342 for an explanation of imap namespaces. but it doesn't work in the imapclient example file. sure its also possible
On Thursday 11 November 2004 15:25, Jp Calderone wrote: that the library works correct, than its a bug in the example file. ;-) -- Regards, Robert ---------- Robert Penz robert dot penz at outertech dot com
On Sun, 14 Nov 2004 18:58:55 +0100, Robert Penz <robert.penz@outertech.com> wrote:
On Thursday 11 November 2004 15:25, Jp Calderone wrote:
It sounds like both the server and Twisted are doing just the right thing. See rfc 2342 for an explanation of imap namespaces.
but it doesn't work in the imapclient example file. sure its also possible that the library works correct, than its a bug in the example file. ;-)
Selecting the appropriate default mailbox to open is beyond the scope of the example. It assumes "inbox" is the right thing, which is true for many servers. Writing something robust which supports all servers is something a real application needs to figure out. Jp
On Nov 14, 2004, at 1:20 PM, Jp Calderone wrote:
Selecting the appropriate default mailbox to open is beyond the scope of the example. It assumes "inbox" is the right thing, which is true for many servers.
Well, that's untrue, the example lets the user select the mailbox to use from the results of LIST *, and doesn't assume anything about inbox. But, "INBOX" is the right default mailbox for *all* servers, according to the IMAP RFC. Perhaps the issue here is that the server doesn't show the "INBOX" special mailbox in its LIST response. I think that's pretty common. James
Hello. I am trying to write simple messaging application to do some automation at my work. I want to use Jabber protocol and hoped to find some "Hello world" client and server code sample for it which works right "out of box" to start from. But looking through the mailing list I found that information on this subject is sparse and all do not work without modification. So here are questions: 1. Seems that jabber protocol support in twisted is very basic and it requires to study JEPs to create even basic application. If so, is there any effort to provide more functionality to Jabber in twisted or I should rely on something like twibber library to use it? Everything I managed to find by now is partial code samples and no working applications which use twisted/Jabber in contrast to other protocols which you can made to work with a handful o lines. 2. Is twisted supposed to be platform independent? There are parts of code which utilize fcntl module which does not work on Windows. So I can not utilize them. Petr.
On Mon, 15 Nov 2004 12:22:38 +0600, Petr Gladkikh <batyi@mail.ru> wrote:
Hello.
I am trying to write simple messaging application to do some automation at my work. I want to use Jabber protocol and hoped to find some "Hello world" client and server code sample for it which works right "out of box" to start from. But looking through the mailing list I found that information on this subject is sparse and all do not work without modification. So here are questions:
1. Seems that jabber protocol support in twisted is very basic and it requires to study JEPs to create even basic application. If so, is there any effort to provide more functionality to Jabber in twisted or I should rely on something like twibber library to use it? Everything I managed to find by now is partial code samples and no working applications which use twisted/Jabber in contrast to other protocols which you can made to work with a handful o lines.
As far as I know, no one is actively improving Twisted's jabber support.
2. Is twisted supposed to be platform independent? There are parts of code which utilize fcntl module which does not work on Windows. So I can not utilize them.
Twisted is not platform independent by any means. It _does_ allow _you_ to write platform independent programs, though. It also exposes useful platform-specific functionality non-uniformly across different platforms, either because no one has requested the functionality on some of those platforms, or because those platforms are incapable of providing said functionality. For the fcntl module in particular, I believe this only restricts you from using the conch client and the generic stdio support on Windows. The rest of Twisted will function fine. Jp
participants (4)
-
James Y Knight -
Jp Calderone -
Petr Gladkikh -
Robert Penz