Yes, I think it would be cleaner overall to have a 'native' chapel library
that wrapped up libev. I'd like to do that.
Agree my example is pretty trivial, but proved to me that what I wanted to
do is straightforward. I've been thinking about the style of Chapel and
built-in assumptions as compared to something like Finagle
<https://twitter.github.io/finagle/>, which is a very SOA-mindset (RPC
failure / timeout / etc is part of the top-level reasoning process.
I think a Chapel library that enabled it to be used as the backend for, say
a web-server, would benefit from helping the developer reason about
downstream timeouts, etc. So I guess there's a basic libev and then
there's a "real" wrapper that helps devs reason about the async world.
On Fri, Mar 27, 2015 at 7:12 AM, Michael Ferguson <[email protected]>
wrote:
> Hi Brian -
>
> Cool! I've been hoping to demonstrate Chapel + libev or libevent.
>
> It looks like your Chapel program pretty much immediately calls
> into a C function that does everything...
>
> Are you thinking about creating libev Chapel library usable by
> others? E.g., what if somebody wanted to use libev in Chapel to create
> a client rather than a server?
>
> Thanks,
>
> -michael
>
> On 3/27/15, 10:06 AM, "Brian Guarraci" <[email protected]> wrote:
>
> >Hi,
> >
> >
> >As part of my project, I'm using Chapel to serve network requests (e.g.
> >web). I have posted a simple integration example here:
> >
> >
> >https://github.com/briangu/libev-examples
> >
> >
> >
> >Cheers!
> >Brian
> >
>
>
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Chapel-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/chapel-developers
