Open mk-pmb opened 7 years ago
FWIW that undocumented option was added by someone else in https://github.com/mscdex/node-imap/pull/388.
Historically speaking, one reason arbitrary streams are not supported is because that's not a common use case.
I guess that implieas there are no intentional reasons. Would you be willing to maintain a branch that uses duplex streams, if someone were to refactor the module?
I dunno at this point. What is your use case anyway?
Currently, IMAP over unix domain socket, using the file system for access control. Will probably evolve to
Hi, thanks for providing an abstraction to the IMAP protocol!
To me the readme looks like the IMAP stuff is mixed up with lots of TCP and TLS stuff though, is that right? I can't even find an API for how to pass my duplex stream that has my IMAP server on the other side. Did I miss something then? Can this module talk to my IMAP server over any duplex stream?
lib/Connection.js
ln 102 looks like there's an undocumentedsocket
option in the config object, but the very next line makes clear that it expects socket-specific features that arbitrary duplex streams don't usually have.Are there special reasons why an IMAP module should care about the transport layer, or could (should?) we refactor the transport stuff to some other module someday?