I'm not sure the suspension egg needs a dependency on a serializer at
all. It would still serve its purpose if continuation-suspend and
continuation-resume passed around the native continuation objects and
let the client do the serialization.
Good point. I will change it accordingly.
And
On 2013-05-30 22:32, Felix wrote:
[...]
Very good - thanks a lot! I'll give this a try. Should we simply replace
the serialization or do you think it would make sense to let the user
choose a serialization mechanism for suspensions?
[...]
Hello Felix,
I'm not sure the suspension egg needs a
yes, I'm aware of suspension and the magic going on inside that egg is
precisely what I referred to by fiddling around with green threads.
In fact, protobuf can easily act as a drop-in replacement for s11n and I
just verified that it does work just fine with suspensions! So I can say
with
Felix scripsit:
Very good - thanks a lot! I'll give this a try. Should we simply replace
the serialization or do you think it would make sense to let the user
choose a serialization mechanism for suspensions?
Given the advantages of PBs, I'd just move to them for all applications of
From: Thomas Chust ch...@web.de
Subject: [Chicken-users] Protocol Buffers for CHICKEN
Date: Wed, 29 May 2013 00:15:20 +0200
Hello,
during the CHICKEN spring thing in Cologne I started to work on a new
egg [1] implementing the protocol buffer [2] serialization format, which
is now
closure serialization definitely works, I have tried round tripping
compiled and interpreted procedures with and without surrounding context
through serialize and deserialize and they are still functional after
reading them back in.
Excellent.
Continuations should work, too, but it is
Hi,
during the CHICKEN spring thing in Cologne I started to work on a new
egg [1] implementing the protocol buffer [2] serialization format, which
is now in a usable and tested state.
Wow! This looks super cool!
I'm so sad to have missed the Spring Thing.
I wonder if you might entertain
Hello,
during the CHICKEN spring thing in Cologne I started to work on a new
egg [1] implementing the protocol buffer [2] serialization format, which
is now in a usable and tested state.
If you don't need or want to use a specific schema for your data, you
can use the protobuf egg as a generic
This is very welcome!
I wonder if this would be useful for storing data in a posix shared
memory block...
-Dan
On 5/28/2013 3:15 PM, Thomas Chust wrote:
Hello,
during the CHICKEN spring thing in Cologne I started to work on a new
egg [1] implementing the protocol buffer [2] serialization
On 2013-05-29 00:32, Dan Leslie wrote:
[...]
I wonder if this would be useful for storing data in a posix shared
memory block...
[...]
Hello Dan,
that is certainly possible, you would just combine serialize and
call-with-output-string to obtain data you can copy into a shared buffer
and
Huh, now that is useful!
https://wiki.call-cc.org/man/4/Unit%20lolevel#object-evict
Still, if I ever have call to use pshm for ipc between chicken and
not-chicken workers then this egg would probably be useful.
Thanks again,
-Dan
On 5/28/2013 5:24 PM, Thomas Chust wrote:
On 2013-05-29
11 matches
Mail list logo
