[
https://issues.apache.org/jira/browse/JAMES-3695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17475120#comment-17475120
]
Benoit Tellier commented on JAMES-3695:
---------------------------------------
Hello Dineth,
Nice! There is many smaller sub-tasks that you could start looking at to get to
know better James & Pulsar.
For instance, you could try to have a look at
https://issues.apache.org/jira/browse/JAMES-3700
Cheers!
> Adopt Pulsar as the messaging technology backing the distributed James server
> -----------------------------------------------------------------------------
>
> Key: JAMES-3695
> URL: https://issues.apache.org/jira/browse/JAMES-3695
> Project: James Server
> Issue Type: Improvement
> Components: mailbox, Queue, task
> Affects Versions: master
> Reporter: Benoit Tellier
> Priority: Major
> Labels: gsoc2022
>
> https://www.mail-archive.com/[email protected]/msg71462.html
> A good long term objective for the PMC is to drop RabbitMQ in
> favor of pulsar (third parties could package their own components using
> RabbitMQ if they wishes...)
> This means:
> - Solve the bugs that were found during the Pulsar MailQueue review
> - Pulsar MailQueue need to allow listing blobs in order to be
> deduplication friendly.
> - Provide an event bus based on Pulsar
> - Provide a task manager based on Pulsar
> - Package a distributed server backed by pulsar, deprecate then replace
> the current one.
> - (optionally) support mail queue priorities
> While contributions would of course be welcomed on this topic, we could
> offer it as part of GSOC 2022, and we could co-mentor it with mentors of
> the Pulsar community (see [3])
> [3] https://lists.apache.org/thread/y9s7f6hmh51ky30l20yx0dlz458gw259
> Would such a plan gain traction around here ?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
