Pike-devel December 2017

pike-devel@lists.lysator.liu.se

7 participants
25 discussions

Concurrent/Promises/Futures docs less scary?
by Stephen R. van den Berg 04 Dec '17

04 Dec '17

Anyone who has been scared away from Promises, should, I think, now take a look at the improved docs (still a lot of room for improvement there, like examples) in Pike 8.1. I changed the wording quite drastically to make it easier to digest. This time it might actually be understandable without feeling like a contortionist. -- Stephen.

1 0

Concurrent and avoid call_out() for most callbacks?
by Stephen R. van den Berg 03 Dec '17

03 Dec '17

In the old code, it was not possible to run the callbacks without incurring deadlocks. After the rewrite now, it's deadlock-free. I tested with and without the call_out() construct. In my testcases, I see: a. Comparable CPU usage for both cases. b. 6% wall-clock speed improvement when avoiding call_out(). I propose ripping out the call_out() method, so that callouts are ran directly in all cases except for the timeout-case. Any objections? -- Stephen.

2 5

A callback when main() returns with -1?
by Stephen R. van den Berg 02 Dec '17

02 Dec '17

Is there a callback when main() returns with -1 and drops into the DefaultBackend? If there is not, can we create one? -- Stephen.

1 1

HTTP.Promise2 vs. HTTP.Promise
by Stephen R. van den Berg 01 Dec '17

01 Dec '17

Are there many users of Protocols.HTTP.Promise already? I made a less filling version, with slightly changed API. The new one is called Protocols.HTTP.Promise2 at the moment; if there are no objections, I'd replace HTTP.Promise with this one. Most notable differences between HTTP.Promise2 and HTTP.Promise: a. Less filling (20% smaller compiled object file). b. Instead of two result objects, we simply have a single HTTP.Promise.Result object which is passed both on_success() and on_failure(). Why does the original separate this in a Promise.Success and Promise.Failure type? c. Various code optimisations, that do not change the interface. d. The Result object lacks the ok() method. What use was/is it? You should normally already know if you are a success or a failure callback. e. The Result object returns the raw body through "data", and the decoded body through get() (to conform more to standard Future objects). -- Stephen.

2 1

SCRAM and docs
by Stephen R. van den Berg 01 Dec '17

01 Dec '17

Two things: a. I see a remark about making that cache-mapping weak. What would that help (it contains strings only)? b. Where did the docs go? I can't seem to find them anywhere. -- Stephen.

2 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Pike-devel December 2017