> On Sep 4, 2015, at 5:26 AM, Dawid Loubser <da...@travellinck.com> wrote: > > And given the vision, experience and efforts of people like Peter, it > would almost be criminal to not break free from an old standard, to miss > the potential of what may be. >
Speaking of which, I’ve always wondered, Peter, if you could tell us a little about the Jini systems you’ve built and worked with in the past, and some of the issues you’ve seen in production? It would be great if we on the list could share some experiences - that would highlight areas where the standards get in the way, and we could change them. We are the standards body for Jini, after all. For myself, the big issue was always ease of writing and deploying services, which is why I wrote the Harvester application container back in the day, and the River Container (which I really must get around to thinking up a new name for) more recently. When you get more than a few machines involved, things get complicated to manage, although I haven’t done a system big enough to show the kind of QOS issues that Dennis’ Rio project was designed to address. Cheers, Greg Trasuk
