|
Bill Allombert on Thu, 12 Sep 2024 18:41:38 +0200
|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
|
Re: Serialization of PARI data as a way of IPC
|
- To: pari-dev@pari.math.u-bordeaux.fr
- Subject: Re: Serialization of PARI data as a way of IPC
- From: Bill Allombert <Bill.Allombert@math.u-bordeaux.fr>
- Date: Thu, 12 Sep 2024 18:41:31 +0200
- Delivery-date: Thu, 12 Sep 2024 18:41:38 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=math.u-bordeaux.fr; s=2022; t=1726159295; bh=3q6Kgnuy3a0EmnQ68GAt4auiKNP3nVsGaOYFBXX8OB8=; h=Date:From:To:Subject:References:In-Reply-To:From; b=kcwGgdV/RpnZu9j34P1GeXxBIuEmvzqac9daAFZx6r6qS7oHS2CJ+Z8WfrCei/TCG LTG5EQlxbWgG5wdICb7QPmnoaRlT7v/vp7T/wygJEjrp6x5ouomFYI5W4OQQnIdrQr x7SJxyEBEOhdk1Q//HpBLYPRSaHlrwWX48RyrUeuzqGzY7+cvogEuq2UL73FSl2vkl A21DXG+pjhtt5VQKHyxHYmwsoIqUE8zs71aSCsKYG0k/sLaSEkMJtKlRz2NEudZr1W vgh4W0I80uSJKlV3NmfKPvnAzwNCH+YWY8M0s1hk7SJcT88iO0EjDQcdZ3S/ZJhyc4 fnObO2kC4PoGIOU8GA++UEpDqXVi7YT3FUL8EnO8tcKY00y4/N1yT1vj3OBrcT8mHO HR0dt9FlyXWvC9GLjAUpOS0h4E2AQAo+MSWBzdgZGagORpgHMt3kCg2hqh7ZmFXL8z l4HnhZWNjyT68zcGspf/FWnQs1bv6s3ehHQOjZ6GFFya6BlVyUlQAP7e2sgIfy/9Ya GE6npxJbXxVZ9FwjmPwE7n1j468G/egk+XfHJyMNu/KsH01wi6R+prMQgopLVPRqh1 DfAgB80TgBFsDOR4n6Kse/gSbhencsviq8oeX4EZuGQrfjy4aivDcBKgpH+j13A7io GZGM/zN++YHKkZcdZQ+t2BDo=
- In-reply-to: <ZuL6R29vFyww67XG@debian.attlocal.net>
- Mail-followup-to: pari-dev@pari.math.u-bordeaux.fr
- References: <ZuL6R29vFyww67XG@debian.attlocal.net>
On Thu, Sep 12, 2024 at 07:27:19AM -0700, Ilya Zakharevich wrote:
> My impression is that when PARI is used as a library inside larger
> heterogeneous-aggregation projects, they use
> stringization/destringization of PARI data as a way of inter-library
> communication. This goes through binary↔decimal conversion.
PARI itself uses binary serialization for MPI, using the bin_copy/copy_bin
mechanism.
The same system could be used for other IPC as long as they can pass
arbitrary data stream.
Cheers,
Bill.