^ but for stable series
they should just work.
--
Cheers,
Tim
--
*From: *Tom Arnfeld t...@duedil.com
*To: *user@mesos.apache.org
*Sent: *Tuesday, July 15, 2014 2:50:47 AM
*Subject: *Re: Mesos language bindings in the wild
Hey Tim,
I can
@mesos.apache.org
*Sent: *Tuesday, July 15, 2014 2:50:47 AM
*Subject: *Re: Mesos language bindings in the wild
Hey Tim,
I can see your point, and am finding it hard to think of any
compelling arguments against the issue of fragmentation, but I do have a
few thoughts.p
That said, I would
: Mesos language bindings in the wild
Hi all,
Apologies for being super late to this thread. To answer Niklas point at
the start of the thread: Yes, I am thrilled to contribute in anyway I can.
The project is moving forward and making progress (slower than I want, but
progress
, Tim St Clair tstcl...@redhat.com wrote:
Inline -
--
*From: *Vladimir Vivien vladimir.viv...@gmail.com
*To: *user@mesos.apache.org
*Sent: *Tuesday, July 15, 2014 1:34:37 PM
*Subject: *Re: Mesos language bindings in the wild
Hi all
.
--
Cheers,
Tim
--
*From: *Tom Arnfeld t...@duedil.com
*To: *user@mesos.apache.org
*Sent: *Tuesday, July 15, 2014 2:50:47 AM
*Subject: *Re: Mesos language bindings in the wild
Hey Tim,
I can see your point, and am finding it hard to think
...@duedil.com
*To: *user@mesos.apache.org
*Sent: *Tuesday, July 15, 2014 2:50:47 AM
*Subject: *Re: Mesos language bindings in the wild
Hey Tim,
I can see your point, and am finding it hard to think of any compelling
arguments against the issue of fragmentation, but I do have a few thoughts.p
:
--
*From: *Niklas Nielsen nik...@mesosphere.io
*To: *user@mesos.apache.org
*Sent: *Thursday, July 17, 2014 1:53:49 PM
*Subject: *Re: Mesos language bindings in the wild
-1 for git submodules. I am really not keen on those; worked with them
while working on Chromium
--
*From: *Tom Arnfeld t...@duedil.com
*To: *user@mesos.apache.org
*Sent: *Tuesday, July 15, 2014 2:50:47 AM
*Subject: *Re: Mesos language bindings in the wild
Hey Tim,
I can see your point, and am finding it hard to think of any compelling
arguments against the issue
: *Tom Arnfeld t...@duedil.com
*To: *user@mesos.apache.org
*Sent: *Tuesday, July 15, 2014 2:50:47 AM
*Subject: *Re: Mesos language bindings in the wild
Hey Tim,
I can see your point, and am finding it hard to think of any compelling
arguments against the issue of fragmentation, but I do
Inline -
- Original Message -
From: Vladimir Vivien vladimir.viv...@gmail.com
To: user@mesos.apache.org
Sent: Tuesday, July 15, 2014 1:34:37 PM
Subject: Re: Mesos language bindings in the wild
Hi all,
Apologies for being super late to this thread. To answer Niklas point
:
Inline -
--
*From: *Vladimir Vivien vladimir.viv...@gmail.com
*To: *user@mesos.apache.org
*Sent: *Tuesday, July 15, 2014 1:34:37 PM
*Subject: *Re: Mesos language bindings in the wild
Hi all,
Apologies for being super late to this thread. To answer Niklas
- Original Message -
From: Niklas Nielsen nik...@mesosphere.io
To: user@mesos.apache.org
Sent: Thursday, July 17, 2014 1:53:49 PM
Subject: Re: Mesos language bindings in the wild
-1 for git submodules. I am really not keen on those; worked with them while
working on Chromium
?
-Tim
- Original Message -
From: Tom Arnfeld t...@duedil.com
To: d...@mesos.apache.org
Cc: user@mesos.apache.org
Sent: Friday, July 11, 2014 10:22:59 AM
Subject: Re: Mesos language bindings in the wild
Very exciting. I'd vote +1 for splitting them out. Especially if you
look
on 'versioning' should come before bindings to ensure
we adhere to policy.
Thoughts?
-Tim
- Original Message -
From: Tom Arnfeld t...@duedil.com
To: d...@mesos.apache.org
Cc: user@mesos.apache.org
Sent: Friday, July 11, 2014 10:22:59 AM
Subject: Re: Mesos language bindings in the wild
-
From: yifan myan...@msn.com
To: user@mesos.apache.org
Sent: Monday, July 14, 2014 7:10:34 PM
Subject: Re: Mesos language bindings in the wild
Hi Tim,
I found that in zookeeper, they also separate the bindings from the core.
https://cwiki.apache.org/confluence/display/ZOOKEEPER
Very exciting. I'd vote +1 for splitting them out. Especially if you
look at the common way of using Go imports, just stick the project on
GitHub and import it directly using github.com/mesos/mesos-go or
similar.
I guess one argument is that you have more fragmentation of the code
(e.g every
I'm a fan of splitting these things out as you end up with various
implementations, some of which will be more suited for some applications
that others. It also encourages exploration of the API in various ways.
As an aside, I've been playing with a go version too at
I'm a fan of splitting these things out as you end up with various
implementations, some of which will be more suited for some applications
that others. It also encourages exploration of the API in various ways.
As an aside, I've been playing with a go version too at
Embraced language repos is a great path too. +1 for not having to tie
automake into the respective language build systems.
Ensuring that they all work together when Mesos is changing becomes a bit
more difficult, but not worse than CI'ing builds of the respective
bindings against HEAD (is bindings
+1, esp re: Go.
Test harness for language bindings will be pretty important.
Cheers,
Tim
- Original Message -
From: Niklas Nielsen nik...@mesosphere.io
To: dev d...@mesos.apache.org
Cc: user@mesos.apache.org
Sent: Thursday, July 10, 2014 5:57:49 PM
Subject: Re: Mesos language
: *Niklas Nielsen nik...@mesosphere.io
*To: *dev d...@mesos.apache.org
*Cc: *user@mesos.apache.org
*Sent: *Thursday, July 10, 2014 5:57:49 PM
*Subject: *Re: Mesos language bindings in the wild
I just wanted to clarify - native, meaning _no_ dependency to libmesos and
native to its language (only
Naming suggestion, let's call these pure language bindings. Native is
overloaded.
On Fri, Jul 11, 2014 at 8:40 AM, Niklas Nielsen nik...@mesosphere.io
wrote:
Embraced language repos is a great path too. +1 for not having to tie
automake into the respective language build systems.
Ensuring
providing language bindings for dynamic languages would probably be a lot
easier if there were a singel default C interface to mesos instead of just
C++.
A language like Rust is very interesting to me but it doesn't have good C++
interop.
It would also be good to just get the internals of how
I just wanted to clarify - native, meaning _no_ dependency to libmesos and
native to its language (only Go, only Python and so on) i.e. use the
low-level API.
Sorry for the confusion,
Niklas
On 10 July 2014 15:55, Dominic Hamon dha...@twopensource.com wrote:
In my dream world, we wouldn't
o ok. Well see swagger http://swagger.wordnik.com/ :)
bindings for everybody.
---
Met vriendelijke groeten - Best regards - Salutations
Ivan Porto Carrero - Mob: +1 (415) 323-8084
Web: http://flanders.co.nz
Twitter: http://twitter.com/casualjim
On Thu, Jul 10, 2014 at 3:57 PM, Niklas Nielsen
25 matches
Mail list logo
