Hi everyone, What is the current state of UDP in Gambit? I found - an old post where Marc says he has preliminary support and - https://github.com/bitwize/gamsock which looks interesting but hasn't been updated in years Anything else available if I need to integrate UDP in my Gambit application? Thanks
You can use UDP sockets through raw devices and ffi. There is a pretty comprehensive socket ffi in Gerbil which you can use with raw Gambit code: https://github.com/vyzo/gerbil/blob/master/src/std/os/_socket.scm Of course you may want to try out Gerbil in full, which has quite good support for sockets with a high level interface: https://github.com/vyzo/gerbil/blob/master/src/std/os/socket.ss -- vyzo On Thu, Aug 3, 2017 at 2:56 PM, Guillaume Cartier <gcartier@jazzscheme.org> wrote:
Hi everyone,
What is the current state of UDP in Gambit?
I found - an old post where Marc says he has preliminary support and - https://github.com/bitwize/gamsock which looks interesting but hasn't been updated in years
Anything else available if I need to integrate UDP in my Gambit application?
Thanks
_______________________________________________ Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list
Gamsock maintainer here. Does Gamsock somehow not fit your needs? I'm open to bug reports or feature requests. On Aug 3, 2017 7:56 AM, "Guillaume Cartier" <gcartier@jazzscheme.org> wrote:
Hi everyone,
What is the current state of UDP in Gambit?
I found - an old post where Marc says he has preliminary support and - https://github.com/bitwize/gamsock which looks interesting but hasn't been updated in years
Anything else available if I need to integrate UDP in my Gambit application?
Thanks
_______________________________________________ Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list
Hey Jeff, I really like what I saw when I browsed Gamsock's code. The code looks clean and well implemented. The two things I see missing, correct me if I'm wrong are: #1 Cross-platform support, mainly Windows #2 Some way to block on reading the UDP port that is integrated with the Gambit scheduler Regarding #1, it seems a bit wasteful to have to implement cross-platform sockets as it is already done in Gambit's low-level C code, so maybe some collaboration with Marc into exposing this code in some way Regarding #2, my understanding is that Marc added raw-device ports a while ago to help vyzo do exactly that in Gerbil On Fri, Aug 4, 2017 at 4:36 PM, Jeff Read <bitwize@gmail.com> wrote:
Gamsock maintainer here. Does Gamsock somehow not fit your needs? I'm open to bug reports or feature requests.
On Aug 3, 2017 7:56 AM, "Guillaume Cartier" <gcartier@jazzscheme.org> wrote:
Hi everyone,
What is the current state of UDP in Gambit?
I found - an old post where Marc says he has preliminary support and - https://github.com/bitwize/gamsock which looks interesting but hasn't been updated in years
Anything else available if I need to integrate UDP in my Gambit application?
Thanks
_______________________________________________ Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list
Regarding #2
Yes, I implemented raw devices exactly for this reason. Gamsock could use the socket ffi from Gerbil to provide the same interface but integrated with the Gambit i/o scheduler, -- vyzo On Wed, Aug 9, 2017 at 6:48 PM, Guillaume Cartier <gcartier@jazzscheme.org> wrote:
Hey Jeff,
I really like what I saw when I browsed Gamsock's code. The code looks clean and well implemented.
The two things I see missing, correct me if I'm wrong are:
#1 Cross-platform support, mainly Windows #2 Some way to block on reading the UDP port that is integrated with the Gambit scheduler
Regarding #1, it seems a bit wasteful to have to implement cross-platform sockets as it is already done in Gambit's low-level C code, so maybe some collaboration with Marc into exposing this code in some way
Regarding #2, my understanding is that Marc added raw-device ports a while ago to help vyzo do exactly that in Gerbil
On Fri, Aug 4, 2017 at 4:36 PM, Jeff Read <bitwize@gmail.com> wrote:
Gamsock maintainer here. Does Gamsock somehow not fit your needs? I'm open to bug reports or feature requests.
On Aug 3, 2017 7:56 AM, "Guillaume Cartier" <gcartier@jazzscheme.org> wrote:
Hi everyone,
What is the current state of UDP in Gambit?
I found - an old post where Marc says he has preliminary support and - https://github.com/bitwize/gamsock which looks interesting but hasn't been updated in years
Anything else available if I need to integrate UDP in my Gambit application?
Thanks
_______________________________________________ Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list
_______________________________________________ Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list
Guillaume, For completeness - when there are userland ports, implementing UDP as a module will be trivial. For more info see here https://github.com/gambit/gambit/issues/288 . Adam 2017-08-09 19:10 GMT+02:00 Dimitris Vyzovitis <vyzo@hackzen.org>:
Regarding #2
Yes, I implemented raw devices exactly for this reason. Gamsock could use the socket ffi from Gerbil to provide the same interface but integrated with the Gambit i/o scheduler,
-- vyzo
On Wed, Aug 9, 2017 at 6:48 PM, Guillaume Cartier <gcartier@jazzscheme.org
wrote:
Hey Jeff,
I really like what I saw when I browsed Gamsock's code. The code looks clean and well implemented.
The two things I see missing, correct me if I'm wrong are:
#1 Cross-platform support, mainly Windows #2 Some way to block on reading the UDP port that is integrated with the Gambit scheduler
Regarding #1, it seems a bit wasteful to have to implement cross-platform sockets as it is already done in Gambit's low-level C code, so maybe some collaboration with Marc into exposing this code in some way
Regarding #2, my understanding is that Marc added raw-device ports a while ago to help vyzo do exactly that in Gerbil
On Fri, Aug 4, 2017 at 4:36 PM, Jeff Read <bitwize@gmail.com> wrote:
Gamsock maintainer here. Does Gamsock somehow not fit your needs? I'm open to bug reports or feature requests.
On Aug 3, 2017 7:56 AM, "Guillaume Cartier" <gcartier@jazzscheme.org> wrote:
Hi everyone,
What is the current state of UDP in Gambit?
I found - an old post where Marc says he has preliminary support and - https://github.com/bitwize/gamsock which looks interesting but hasn't been updated in years
Anything else available if I need to integrate UDP in my Gambit application?
Thanks
_______________________________________________ Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list
_______________________________________________ Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list
_______________________________________________ Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list
Ports are not the right abstraction for UDP -- UDP sockets are not streams of bytes, so userland ports are not relevant. --vyzo On Fri, Aug 11, 2017 at 9:28 PM, Adam <adam.mlmb@gmail.com> wrote:
Guillaume,
For completeness - when there are userland ports, implementing UDP as a module will be trivial.
For more info see here https://github.com/gambit/gambit/issues/288 .
Adam
2017-08-09 19:10 GMT+02:00 Dimitris Vyzovitis <vyzo@hackzen.org>:
Regarding #2
Yes, I implemented raw devices exactly for this reason. Gamsock could use the socket ffi from Gerbil to provide the same interface but integrated with the Gambit i/o scheduler,
-- vyzo
On Wed, Aug 9, 2017 at 6:48 PM, Guillaume Cartier < gcartier@jazzscheme.org> wrote:
Hey Jeff,
I really like what I saw when I browsed Gamsock's code. The code looks clean and well implemented.
The two things I see missing, correct me if I'm wrong are:
#1 Cross-platform support, mainly Windows #2 Some way to block on reading the UDP port that is integrated with the Gambit scheduler
Regarding #1, it seems a bit wasteful to have to implement cross-platform sockets as it is already done in Gambit's low-level C code, so maybe some collaboration with Marc into exposing this code in some way
Regarding #2, my understanding is that Marc added raw-device ports a while ago to help vyzo do exactly that in Gerbil
On Fri, Aug 4, 2017 at 4:36 PM, Jeff Read <bitwize@gmail.com> wrote:
Gamsock maintainer here. Does Gamsock somehow not fit your needs? I'm open to bug reports or feature requests.
On Aug 3, 2017 7:56 AM, "Guillaume Cartier" <gcartier@jazzscheme.org> wrote:
Hi everyone,
What is the current state of UDP in Gambit?
I found - an old post where Marc says he has preliminary support and - https://github.com/bitwize/gamsock which looks interesting but hasn't been updated in years
Anything else available if I need to integrate UDP in my Gambit application?
Thanks
_______________________________________________ Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list
_______________________________________________ Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list
_______________________________________________ Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list
Just to clarify this last one a bit. I was referring to the classic byte/character/object port abstraction. With the introduction of raw devices, we have a new base class of ports, which are the waitable ports. These objects are i/o objects managed by the Gambit runtime and integrated with the Gambit scheduler. The idea is that there exist i/o objects that don't fit the stream abstraction, and we would like to do i/o on them using specialized (ffi) methods while integrating with the Gambit scheduler. UDP sockets is perfect example of such a device: they are not streams of bytes, so they don't fit the classic port abstraction. But they are i/o objects, on which you can do i/o with specialized ffi methods and you want to integrate with the Gambit scheduler to avoid blocking or spinning. -- vyzo On Sat, Aug 12, 2017 at 8:55 AM, Dimitris Vyzovitis <vyzo@hackzen.org> wrote:
Ports are not the right abstraction for UDP -- UDP sockets are not streams of bytes, so userland ports are not relevant.
--vyzo
On Fri, Aug 11, 2017 at 9:28 PM, Adam <adam.mlmb@gmail.com> wrote:
Guillaume,
For completeness - when there are userland ports, implementing UDP as a module will be trivial.
For more info see here https://github.com/gambit/gambit/issues/288 .
Adam
2017-08-09 19:10 GMT+02:00 Dimitris Vyzovitis <vyzo@hackzen.org>:
Regarding #2
Yes, I implemented raw devices exactly for this reason. Gamsock could use the socket ffi from Gerbil to provide the same interface but integrated with the Gambit i/o scheduler,
-- vyzo
On Wed, Aug 9, 2017 at 6:48 PM, Guillaume Cartier < gcartier@jazzscheme.org> wrote:
Hey Jeff,
I really like what I saw when I browsed Gamsock's code. The code looks clean and well implemented.
The two things I see missing, correct me if I'm wrong are:
#1 Cross-platform support, mainly Windows #2 Some way to block on reading the UDP port that is integrated with the Gambit scheduler
Regarding #1, it seems a bit wasteful to have to implement cross-platform sockets as it is already done in Gambit's low-level C code, so maybe some collaboration with Marc into exposing this code in some way
Regarding #2, my understanding is that Marc added raw-device ports a while ago to help vyzo do exactly that in Gerbil
On Fri, Aug 4, 2017 at 4:36 PM, Jeff Read <bitwize@gmail.com> wrote:
Gamsock maintainer here. Does Gamsock somehow not fit your needs? I'm open to bug reports or feature requests.
On Aug 3, 2017 7:56 AM, "Guillaume Cartier" <gcartier@jazzscheme.org> wrote:
Hi everyone,
What is the current state of UDP in Gambit?
I found - an old post where Marc says he has preliminary support and - https://github.com/bitwize/gamsock which looks interesting but hasn't been updated in years
Anything else available if I need to integrate UDP in my Gambit application?
Thanks
_______________________________________________ Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list
_______________________________________________ Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list
_______________________________________________ Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list
And to conclude this rant, I shall be blunt.
For completeness - when there are userland ports, implementing UDP as a module will be trivial.
UDP is already done with raw devices. There is an ffi module you can use for sockets in Gerbil, which is distributed with the same license as Gambit and you can use in your Gambit programs without waiting for whatever these userland ports are. Similarly, Gamsock can also be easily updated to use raw devices with the it's existing interface but without the spinning. -- vyzo On Sat, Aug 12, 2017 at 9:28 AM, Dimitris Vyzovitis <vyzo@hackzen.org> wrote:
Just to clarify this last one a bit.
I was referring to the classic byte/character/object port abstraction.
With the introduction of raw devices, we have a new base class of ports, which are the waitable ports. These objects are i/o objects managed by the Gambit runtime and integrated with the Gambit scheduler. The idea is that there exist i/o objects that don't fit the stream abstraction, and we would like to do i/o on them using specialized (ffi) methods while integrating with the Gambit scheduler.
UDP sockets is perfect example of such a device: they are not streams of bytes, so they don't fit the classic port abstraction. But they are i/o objects, on which you can do i/o with specialized ffi methods and you want to integrate with the Gambit scheduler to avoid blocking or spinning.
-- vyzo
On Sat, Aug 12, 2017 at 8:55 AM, Dimitris Vyzovitis <vyzo@hackzen.org> wrote:
Ports are not the right abstraction for UDP -- UDP sockets are not streams of bytes, so userland ports are not relevant.
--vyzo
On Fri, Aug 11, 2017 at 9:28 PM, Adam <adam.mlmb@gmail.com> wrote:
Guillaume,
For completeness - when there are userland ports, implementing UDP as a module will be trivial.
For more info see here https://github.com/gambit/gambit/issues/288 .
Adam
2017-08-09 19:10 GMT+02:00 Dimitris Vyzovitis <vyzo@hackzen.org>:
Regarding #2
Yes, I implemented raw devices exactly for this reason. Gamsock could use the socket ffi from Gerbil to provide the same interface but integrated with the Gambit i/o scheduler,
-- vyzo
On Wed, Aug 9, 2017 at 6:48 PM, Guillaume Cartier < gcartier@jazzscheme.org> wrote:
Hey Jeff,
I really like what I saw when I browsed Gamsock's code. The code looks clean and well implemented.
The two things I see missing, correct me if I'm wrong are:
#1 Cross-platform support, mainly Windows #2 Some way to block on reading the UDP port that is integrated with the Gambit scheduler
Regarding #1, it seems a bit wasteful to have to implement cross-platform sockets as it is already done in Gambit's low-level C code, so maybe some collaboration with Marc into exposing this code in some way
Regarding #2, my understanding is that Marc added raw-device ports a while ago to help vyzo do exactly that in Gerbil
On Fri, Aug 4, 2017 at 4:36 PM, Jeff Read <bitwize@gmail.com> wrote:
Gamsock maintainer here. Does Gamsock somehow not fit your needs? I'm open to bug reports or feature requests.
On Aug 3, 2017 7:56 AM, "Guillaume Cartier" <gcartier@jazzscheme.org> wrote:
> Hi everyone, > > What is the current state of UDP in Gambit? > > I found > - an old post where Marc says he has preliminary support and > - https://github.com/bitwize/gamsock which looks interesting but > hasn't been updated in years > > Anything else available if I need to integrate UDP in my Gambit > application? > > Thanks > > _______________________________________________ > Gambit-list mailing list > Gambit-list@iro.umontreal.ca > https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list > >
_______________________________________________ Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list
_______________________________________________ Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list
participants (4)
-
Adam -
Dimitris Vyzovitis -
Guillaume Cartier -
Jeff Read