Re: cyrus-imapd 3.0.0 next beta and release plan?

[Ken Murchison via Cyrus-devel]

The main motivation was that I/we wanted this completely contained 
within Cyrus rather than using an external service.  A second, and 
minor, motivation was that I wanted to prove that I could do it.  A lot 
of the code needed was already in place from the other services.



On 12/29/2015 02:38 PM, Thomas Jarosch wrote:

Hi Ken,

Am 29.12.2015 um 16:32 schrieb Ken Murchison:

If all that can be done safely in the signal handler is setting a global 
variable,
I might just scrap the heartbeat functionality. The alternative is that the 
actual method processin
code will have periodically check the status of the global variable.  Or do you 
have a more creative idea?

checking a global variable is how it's done usually. Or if the HTTP server
is using some kind of event driven framework, set up a timer instead of SIGARLM.
  
On linux there's signalfd(), but that's non-portable, so a no no for cyrus.


The global variable should be of type "volatile sig_atomic_t".



Random side note: What was the main motivation for implementing
an own HTTP server including authentication stuff / chunked encoding etc?

Was implementing an Apache httpd module in C considered without
redoing the whole HTTP protocol layer? Just wondering,
we are doing our stuff at dayjob as a C++ apache module.
You just register a handler for URIs / mime-types you are interested in.

Other HTTP server like ngix would probably work, too.

Cheers,
Thomas



--
Kenneth Murchison
Principal Systems Software Engineeer
Carnegie Mellon University

Re: cyrus-imapd 3.0.0 next beta and release plan?

[Ken Murchison via Cyrus-devel]

Thomas,

If all that can be done safely in the signal handler is setting a global 
variable, I might just scrap the heartbeat functionality. The 
alternative is that the actual method processing code will have 
periodically check the status of the global variable.  Or do you have a 
more creative idea?




On 12/29/2015 09:44 AM, Thomas Jarosch wrote:

On Sunday, 27. December 2015 09:48:46 Bron Gondwana via Cyrus-devel wrote:

I think I'd like to do the next beta after CalConnect, which is Jan 10-15.
Ken and I will both be working on making sure the calendaring is really
solid.  My main goal from this calconnect is to get our test cases up to
scratch and integrate with Apple's CalTester in Cassandane so we get the
benefit of their tests too.

if you and Ken are going to touch the CalDAV stuff, there's still the issue
in httpd.c's keep_alive() function calling non-trivial code that might
malloc() and therefore block the whole process.

This is what I wrote back then in the email on 2015-09-01
titled "cyrus 2.4 deadlock identified: SIGALRM race":

---
@Ken: The keep_alive() function in httpd.c (CalDAV)
probably suffers from the same signal handler issue.
---

Cheers,
Thomas



--
Kenneth Murchison
Principal Systems Software Engineer
Carnegie Mellon University

Re: cyrus-imapd 3.0.0 next beta and release plan?

[Bron Gondwana via Cyrus-devel]

On Tue, Dec 22, 2015, at 21:31, Ondřej Surý via Cyrus-devel wrote:
> Hey folks,
> 
> do you already have a release plan for cyrus-imapd 3.0.0? The next
> Debian stable will freeze sometime next year, so I need to make a
> decision whether I should make an effort to package 2.5.x, or just wait
> for 3.0.0 final (if you release it in the first half of 2016).
> 
> Also next beta of 3.0.0 would be appreciated ;).

We had a beta nearly ready to go, and it was blocked because writing
the release notes was a big job.

I think I'd like to do the next beta after CalConnect, which is Jan 10-15.
Ken and I will both be working on making sure the calendaring is really
solid.  My main goal from this calconnect is to get our test cases up to
scratch and integrate with Apple's CalTester in Cassandane so we get
the benefit of their tests too.

(and of course get all Robert's JMAP work integrated!)

Bron.


-- 
  Bron Gondwana
  br...@fastmail.fm

cyrus-imapd 3.0.0 next beta and release plan?

[Ondřej Surý via Cyrus-devel]

Hey folks,

do you already have a release plan for cyrus-imapd 3.0.0? The next
Debian stable will freeze sometime next year, so I need to make a
decision whether I should make an effort to package 2.5.x, or just wait
for 3.0.0 final (if you release it in the first half of 2016).

Also next beta of 3.0.0 would be appreciated ;).

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server