Steve: Developing on the Edge

Thoughts on development, Web-services, technology and mountains.

23May
Mon2005

Alpine-style

Stefan Tilkov is signed up as a developer.

We haven't written any of Alpine yet; I have been too busy in the depths of WSRF/WSDM derived specs to do anything, and am busy with getting a proto of something together for the end of June. As and when I come around to implementing the remote deployment API I've designed, then I'll have to sit down and do Alpine.

There is already space for it in the SmartFrog CVS tree; it will be an LGPL project and all participants will be welcome. Ted Neward offered some time too, which would be great.

The name Alpine comes from Alpine-Style as opposed to Himalayan-Style mountaineering. Classic Himalayan is all about big-teams, national governments, many sherpas, reaching the top through brute force. Alpine style is fast, lightweight, risk taking. Succeed through speed. Makes sense, doesn't it?

Posted by steve at 16:25

Comments

new comment thread


	Yes !reply to this thread On 24 May 2005 at 20: 30 Roger commented: Hi, I too very much liked your "thinking the java soap stack" paper. I thought the same for quite a while - so much so that I've written (what I think is) a lightweight, annotations-driven, XML-centric, java WS toolkit supporting 'plain' and wsrf web services. I've not bothered with rpc/encoding and the sun web services specifications. It's called RogsA, and will have a BSD license. As of yet there's no URL ... :( I can keep you informed if you would like ... I'm also very interested in tracking how Alpine develops. Thanks, Roger
	Mrreply to this thread On 25 May 2005 at 14: 43 Anton Tagunov commented: Hi, Steve! All is good and nifty and sweet, but what are your reasons to go for LGPL? Maybe it's just a habbit, but I got very much used to ASL. Why not?
	LGPL plus ASLreply to this thread On 25 May 2005 at 16: 04 Steve Loughran commented: why LGPL? Because that is what we use in smartfrog. But with the very relaxed interpretation of "L": subclassing and importing dont constitute library extension, just use. The issue here is that the Apache board arent happy wit h this, which is why you cant use spring in ASF projects. But once peace breaks out, we can share properly.