Plans for hoodiecrow?

[Marcus Cavanaugh]

Hey folks,

We're planning to replace our existing fake IMAP server for Firefox OS Email with andris9/hoodiecrow.

Browsercrow, the self-described "hacky" browser port of hoodiecrow, is under whiteout-io on GitHub. Do you plan to maintain browsercrow as an active fork of hoodiecrow, or is it solely for packaging changes (as it looks to currently be)?

For our testing needs, the IMAP server's runtime doesn't really matter, but if any of you had plans to pursue further work on a certain port, we'd like to select an upstream for which it'd be most useful for us to contribute back.

Marcus

[Andris Reinman]

Browsercrow is not a long term project, it is a hacky port that runs in browser environment and uses a mocked TCP listener in order to run IMAP client integration tests in Phantomjs. Ideally this should be supported directly by Hoodiecrow – it should detect the environment and act accordingly, just like BrowserBox does which can run both in browser and Node.js without modifications. 

Porting browser support back to Hoodiecrow is so low-priority for us right now that I don’t see it happening any time soon. So far whenever there is something that needs to be changed, I have done this in Hoodiecrow first and then – if needed – ported the change to Browsercrow and not the other way around. Browsercrow already supports all our use cases, so it doesn’t need to be updated anyway.

So if your question was whether to use Hoodiecrow or Browsercrow, then the answer is Hoodiecrow.

Best regards,

Andris

--
You received this message because you are subscribed to the Google Groups "Email.js Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to emailjs+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Whiteout Networks GmbH c/o Werk1

Grafinger Str. 6

D-81671 München

Geschäftsführer: Oliver Gajek

RG München HRB 204479

[Marcus Cavanaugh]

Just the kind of clarification I needed. Thanks!