Ami Ganguli wrote:

> Alan Knowles wrote:
>
>> http://www.akbkhome.com/Projects/phpmole-IDE/FAQ/midgard%20connection.html 
>>
>
>
> Alan,
>
> I've been looking at your midgard_reciever.  I have a few other things 
> I want to work on that require a similar interface (and I actually 
> have some time now to work on this).  How would you feel about moving 
> to XMLRPC?  It's more complex than the HTTP_POST_VARS you're using 
> now, but it's more standard and makes it easier to transfer complex 
> structures. 

quite keen, the only bit I'm not sure about is  how the client end on 
phpmole will work.
 - at present it maps an  midgard object into a 'php class' - where roughly:
- each attribute is a class variable
- multiple value element become arrays (Eg. parameters and members)
My assumtion on the xmlrpc would be that you would have to have a class 
defined on the sending end to match the recieving end. -  which may grow 
the code a little.

for some reason I had some problems with the latest reciever on one 
server - that oldadmin and nadmin refused to upload the file as it was 
too big.. - only worked when I striped all the spaces/comments etc.

I did start having a look at other ways of doing the current system - 
the first step was to experiment using simple htmlspecialchars on the 
text output (rather than CDATA), then using standard expat/ php_xml to 
parse the input rather than the cheesy preg_matching that is done at 
present.

>
> I'd like, for example, to be able to transfer sub-trees without 
> needing repligard.  I think it's easier to do this with XMLRPC, since 
> I can build a tree structure using nested arrays or structs. 


It could still be done with the current method - I guess the only 
downside is that it currently has to do a object->array conversion prior 
to sending

anyway - let me know if you get anywhere - It would be nice to have the 
midgard layer as a pretty mutch 'independant' xmlrpc layer , that other 
web services could use...

regards
alan

>
>
> Regards,
> Ami.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>




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

Reply via email to