Hi,
As it happens I joined the Turbine list a few days ago :)
Unfortunately I'm still quite busy for a client project, which is why
I'm just now catching up on the discussion here. I think building
XML-RPC into Turbine would be a great thing for several reasons, so I
definitely don't want to stand in the way of it.
For one thing, I haven't made any changes in the XML-RPC library for
some months because it has been working well for me, so having a new
environment and more active developers could help to revive development
and bring new features and improvements.
The current license (http://helma.at/hannes/xmlrpc/license.txt) is kept
very simple on purpose and I think should work for most purposes.
However I'm not a very license-savvy person, so just let me know if a
different license would help.
Hannes
Christopher Elkins wrote:
>
> Joshua Lucas [[EMAIL PROTECTED]] wrote:
> > > Your help would be much appreciated! (You definitely have a leg up on me
> > with
> > > all this.) We'll need some client code for those services that are
> > accessed
> > > remotely. Will your com.barista.rpc package work?
> > >
> >
> > Honestly, that's a great question! :)
> >
> > Once Hannes finished his library, I pretty much stopped my own development
> > and worked with his. Let me look over the code tonight and get back to you.
> > If mine doesn't work, I do feel very comfortable with Hannes' so I can help
> > either way.
> >
> Ah, that explains why your page hasn't been updated in, ahem, a while. ;) I too
> am growing increasingly familiar with Hannes' code, but I don't know all of
> the licensing repercussions of using it (i.e., can we re-package his code
> under the Apache license?). Maybe he can tell us. (Hannes, are you out there?)
>
> --
> Christopher Elkins
>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
