Hi all:
A while ago I mentioned that I had taken work on the surrogate container over
to Github to try out both git and a Maven-based build.
It’s now reached an interesting milestone and I’d like to talk about bringing
it back into the River project. Right now, you can startup the container
I'd suggest that you keep it on GitHub, or we bring that and Rio into River at
the same time.
Regards
Dennis
On Nov 28, 2013, at 1123AM, Greg Trasuk tras...@stratuscom.com wrote:
Hi all:
A while ago I mentioned that I had taken work on the surrogate container over
to Github to try out
I’m all for bringing Rio in at the same time! It’s good to have choices. Is
the code provenance clear?
I think we can all agree that telling anyone to start writing services using
only the JTSK is cruel and unusual punishment. In the same way that someone
who wants to write a servlet does
On Nov 28, 2013, at 12:59 PM, Dennis Reedy dennis.re...@gmail.com wrote:
On Nov 28, 2013, at 1159AM, Greg Trasuk tras...@stratuscom.com wrote:
I’m all for bringing Rio in at the same time! It’s good to have choices.
Perhaps what we should also focus on is to create (or move
On Nov 28, 2013, at 244PM, Greg Trasuk tras...@stratuscom.com wrote:
On Nov 28, 2013, at 12:59 PM, Dennis Reedy dennis.re...@gmail.com wrote:
On Nov 28, 2013, at 1159AM, Greg Trasuk tras...@stratuscom.com wrote:
I’m all for bringing Rio in at the same time! It’s good to have
