Pike-devel August 2021

pike-devel@lists.lysator.liu.se

1 participants
2 discussions

Pike Meet-up 2018-Q1
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 20 Oct '21

20 Oct '21

Hi. At Pike Conference 2017 it was decided that we ought to hold a more informal meeting in Linköping ~ once every quarter. As the three month mark from the conference is coming up soon, it seems time to announce the first such meeting for 2018: Pike Meet-up 2018-Q1 Date: 2018-02-03 (Sat) Time: 10:00 - afternoon/evening Place: Roxen IS AB S:t Larsgatan 22A Linköping Welcome! /grubba

2 13

Bleeding-edge Pike broadly operable - code review appreciated
by Chris Angelico 25 Aug '21

25 Aug '21

I just pushed a few changes to master that get the build working (on 64-bit Debian Linux, no other platforms tested). They're mostly small changes and I hope they won't break anything. This actually gets "make doc" happy again after a good while, so it would be really awesome if I haven't just broken something unrelated :) There's another, more significant, change that happened in the past few months. It's not a simple fix. The default behaviour of Protocols.DNS.async_host_to_ip, which is used by Protocols.HTTP, changed from "only look up A records" to "look up AAAA and A records, and return the first AAAA if found, otherwise the first A". Unfortunately everything is built to assume that there's at most one IP address for that host name. The ultimate solution would be to have an asynchronous "establish connection" call, which will do an async DNS lookup, then attempt to connect to each IP in turn until one succeeds. That would require some other changes, and I'm not sure how it would interact with HTTP keep-alive, for instance. As a lesser solution, would it be reasonable to have a method like Protocols.DNS.prefer_ipv4() to invert the return order of DNS records? ChrisA

4 12

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 August 2021