Ah. Well, then I do not think there is anything to worry about as far as
Etch is concerned. There are many, many potential growth points for the
project. A simple example, Etch supports Java and C# language bindings today
with a binary-transport. One of the committers, Seth Call, is working on a
JavaScript language-binding with a JSON-encoded transport. I am working on a
Python binding. Language bindings and transport plugins represent huge
"itches". Furthermore, even our own limited experience has show that even
when one architects language and transport neutrality, we miss stuff. The
python language binding work early on inspired etch changes and
binary-transport changes to better support dynamically typed languages.

Other dimensions of "itches" exists in the management and aggregation of
multiple instances of services. IS-A vs HAS-A relationships between
services. Session management. Service discovery, etc.

IMHO while etch-1.0 offers capabilities today that fix a lot of problems in
the way services are defined, implemented and consumed. I do not by any
means think it eliminates problems from this space entirely. I think was
Etch offers is a more efficient refactoring of the problem of network
service creation and development and in turn "opens the field" to a
completely new class of technological challenges and opportunities.


--
James


On 8/1/08 8:50 AM, "Niclas Hedhman" <[EMAIL PROTECTED]> wrote:

> On Friday 01 August 2008 21:10, James Dixson wrote:
>> I am a bit confused though about the "too good" concern, I do not think I
>> understand what you mean. Could you elaborate?
> 
> I think it was Stefano Mazzocchi who said about community building, that the
> only "Bad Code + Great Vision" will succeed in building strong communities.
> It refers to the fact that there must be "itches to scratch" for a lot of
> people, otherwise they just stay users and the momentum of the project never
> really get going...
> 
> 
> Cheers

-- 
James Dixson
Manager, Software Development
CUAE Engineering, Cisco Systems
(e) [EMAIL PROTECTED]
(p) 512-336-3305
(m) 512-968-2116



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to