Hello,
While writing my proposal I came across 2 important issues related to the
Javascript Client for the Mailman project that have yet to be raised:
1. What I initially had in mind, was to build a Mailman client in
Javascript that provides the same API and functionality that the current
one in
Hey David, here are my thoughs on the challenges:
1) Determine which messages to include in the mbox.
An entire list archive is clearly one choice, but is there also
interest in generating mbox files for specific threads, list archieves
between specific dates, etc.?
Hmm, depending on the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 25.03.2015 um 07:51 schrieb Ana Badescu:
Hello,
While writing my proposal I came across 2 important issues related
to the Javascript Client for the Mailman project that have yet to
be raised:
1. What I initially had in mind, was to build
Hey,
On Wed, Mar 25, 2015 at 12:21 PM, Ana Badescu anabee.em...@gmail.com
wrote:
Hello,
While writing my proposal I came across 2 important issues related to the
Javascript Client for the Mailman project that have yet to be raised:
1. What I initially had in mind, was to build a Mailman
Another *very* nice way to handle asynchronous behaviour in JS (and
one the avoids callback hell) is the Promises paradigm. Promises are a
native ES6 feature per-spec, but not all platforms support it. Node
doesn't, but there's a drop-in polyfill[1] and a number of other
libraries you could
Thanks for your feedback Aurelien.
we'll need something like a task queue and a daemon process or a cron job
In my proposal I suggested using any of several asynchronous job queue
libraries, such as Celery or Huey. These all use redis as a back-end.
Because I have no experience with
Ankush Sharma writes:
I cannot comment on this as I am a student just like you.
First, thank you very much for commenting in the first place!
Students helping each other is one of the most exciting aspects of
GSoC.
But I think you misunderstand student in the context of GSoC. It's
an
Florian Fuchs writes:
The intended audience are folks who use JS, so I'd rather not have
a client that runs on node but looks like Python. :-)
+1
2. I'd also like to make part of the project, a node.js application
that uses the Mailman Javascript client and offers all the
David Udelson writes:
Thanks for your feedback Aurelien.
we'll need something like a task queue and a daemon process or a cron job
In my proposal I suggested using any of several asynchronous job queue
libraries, such as Celery or Huey. [...]
So far, this is good discussion for
My proposal has been updated. I apologize if I breached mailing-list
ediquette, I'll get the hang of this eventually :)
On Wed, Mar 25, 2015 at 10:14 PM, Stephen J. Turnbull
turnb...@sk.tsukuba.ac.jp wrote:
David Udelson writes:
Thanks for your feedback Aurelien.
we'll need
David Udelson writes:
My proposal has been updated. I apologize if I breached mailing-list
ediquette, I'll get the hang of this eventually :)
No etiquette problem. Those are my personal views about effective use
of the mailing list and Melange, respectively. I suspect from past
experience
Hi guys,
I have updated my application on melange for A Dashboard for
Admins/Owners/Moderators project. Reviews on it are welcome.
Regards,
Shreyas Lakhe
___
Mailman-Developers mailing list
Mailman-Developers@python.org
On Thu, Mar 26, 2015 at 4:05 AM, Stephen J. Turnbull step...@xemacs.org
wrote:
Florian Fuchs writes:
If you want to go in that
direction, you'd have to address the question why does this
application want to (mostly) run disconnected?
The Javascript client is actually a node.js module, and
Ana Badescu writes:
The Javascript client is actually a node.js module, and users will be able
to use it as part of a node.js application which just as Postorious, is
server-side.
Oops, that's right, the REST API normally isn't exposed except to
localhost. My bad.
However, we can set
14 matches
Mail list logo
