On Thu, Sep 23, 2010 at 12:49 AM, Miguel Cobá <miguel.coba@gmail.com> wrote:

El mié, 22-09-2010 a las 19:16 -0300, Germán Arduino escribió:

...

Hi Everybody:

I reorganized the XMLRPC packages, integrating the changes of Skrish (currently on PharoGoodies) renaming the packages in four categories:

XMLRPC-Client-Core XMLRPC-Client-Tests XMLRPC-Server-Core XMLRPC-Server-Tests

Next step: Build the following metacello configurations:

ConfigurationOfXMLRPCClient ConfigurationOfXMLRPCServer ConfigurationOfXMLRPCAll

You don't need three configurations, just create one and create 3 groups 'All','Server', 'Client'.

You were faster than :) I was going to answer exactly the same...one ConfigurationOfXMLRPC and different groups: - 'All' - 'Server' - 'Server with Tests' - 'Client' - 'Client with Tests' -etc.... Check ConfigurationOfMagma since it does almost the same I think. cheers mariano Cheers

...

I want to ask to any person wanting to contribute with XMLRPC project take contact with me to coordinate efforts.

Cheers.

-- Miguel Cobá http://miguel.leugim.com.mx

_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Started working on the tests, the current Encoder/Decoder (at client level) works ok. For example, I opened an account on http://snipplr.com (to save useful and interesting Smalltalk snippets) and can connect without problems. Next, some examples: | url proxy r | url := Url absoluteFromText: 'http://snipplr.com/xml-rpc.php'. proxy := XMLRPCProxy new url: url. r := proxy invokeMethod: 'languages.list' withArgs: #('Your snipplr key'). r := proxy invokeMethod: 'user.checkkey' withArgs: #('Your snipplr key'). r := proxy invokeMethod: 'snippet.list' withArgs: #('Your snipplr key' 'pharo'). "To get a snippet you don't need key, but the Snippet ID" r := proxy invokeMethod: 'snippet.get' withArgs: #('41365'). The complete Snipplr xmlrpc API is on: http://snipplr.com/blog/2006/07/06/snipplr-api/ Next step is check the complete API specification (http://www.xmlrpc.com/spec.) to implement all the features at client level. As usual, any comment, suggestion or criticism is more than welcome. Cheers. 2010/9/23 Germán Arduino <garduino@gmail.com>:

ok, ConfigurationOfXMLRPC is on MetacelloRepository, documentation on #workspace method.

Suggestions or corrections from the Metacello experts are more than welcome.

Next Step: The real work start now :)

Cheers. Germán.

2010/9/23 Mariano Martinez Peck <marianopeck@gmail.com>:

...

On Thu, Sep 23, 2010 at 12:49 AM, Miguel Cobá <miguel.coba@gmail.com> wrote:

...

El mié, 22-09-2010 a las 19:16 -0300, Germán Arduino escribió:

...

Hi Everybody:

I reorganized the XMLRPC packages, integrating the changes of Skrish (currently on PharoGoodies) renaming the packages in four categories:

XMLRPC-Client-Core XMLRPC-Client-Tests XMLRPC-Server-Core XMLRPC-Server-Tests

Next step: Build the following metacello configurations:

ConfigurationOfXMLRPCClient ConfigurationOfXMLRPCServer ConfigurationOfXMLRPCAll

You don't need three configurations, just create one and create 3 groups 'All','Server', 'Client'.

You were faster than :) I was going to answer exactly the same...one ConfigurationOfXMLRPC and different groups: - 'All' - 'Server' - 'Server with Tests' - 'Client' - 'Client with Tests' -etc....

Check ConfigurationOfMagma since it does almost the same I think.

cheers

mariano

...

Cheers

...

I want to ask to any person wanting to contribute with XMLRPC project take contact with me to coordinate efforts.

Cheers.

-- Miguel Cobá http://miguel.leugim.com.mx

_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Hi Sven: To be honest I haven't looked at Zn* yet. I know (and use) WebClient and imagine that Zn have similar features? Anyway I have not problem in use the things the Board consider better, but need to make the things step at step. At the server side I really don't looked deeper neither yet, because the main goal of the project is having a xmlrpc client capable of interact with any xmlrpc exposed api, implementing the full specification. Cheers and thanks by the comment. 2010/10/3 Sven Van Caekenberghe <sven@beta9.be>:

Germán,

On 03 Oct 2010, at 17:41, Germán Arduino wrote:

...

As usual, any comment, suggestion or criticism is more than welcome.

Well, you could consider using the Zinc HTTP Components framework.

XMLRPCProxy>>#sendXmlRpc: is using the ugly HTTPSocket interface.

Using any of the clients in Zn will give you a semantically much richer interface to headers and content (entities), both for requests and for responses. And you get many features on top.

I haven't looked at the server side, but there too you can get HTTP functionality for free.

It will add a dependency though, but I would guess you have one for the server side already, no ?

Anyway, we're looking for users...

Sven

_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project