Forum Moderators: coopster

Message Too Old, No Replies

PHP CODE Help: Photoleech integration

PHP XML-RPC coding help

         

iosoft

8:13 am on Jan 25, 2008 (gmt 0)



Dear Friends,

I tried the project myself for an year, but failed and non of my local friends know / interested in it. So, if you kindly help me... I will be very very thankful to you.

Please please help me.

The Project -
I am building India's 1st Tech Portal web-site. BETA is running
<snip>
It will have its own custom gallery system on which I need help from you.

To final host, I have 2 options -
1. Fast server, Low webspace
2. Slow server, Big webspace

I have chosen Fast server, Low webspace.

The Objective -
I want to use <snip> as my partner in hosting all the images (articles and gallery system) of my site. Photoleech has its own API system (XML-RPC) that can be used to integrate with their system with my site.
<snip>
Using this, we can control the Photoleech a/c from my own website control panel as if everything is within my site.

The Problem / Task -
Though I have knowledge on PHP, XML, MySQL, but we have hardly any experience on XML-RPC coding.

So, if you kindly help me on coding the core login, list-images, upload-images (these 3s only) then I will be very very thankful to you.

Please please help us.....

[edited by: dreamcatcher at 8:32 am (utc) on Jan. 25, 2008]
[edit reason] no urls as per T.O.S [webmasterworld.com].Thanks [/edit]

eelixduppy

1:49 am on Jan 29, 2008 (gmt 0)



Hello and Welcome to WebmasterWorld!

You will probably find the information you are looking for in the XML-RPC Specification [xmlrpc.com]. Take a quick read there to figure out how everything should be and then if you need help with the implementation then we're here for you. I do encourage you to try to code this yourself first, however, before asking someone here to code it for you; after all, we do not do each other's homework :)

vincevincevince

1:57 am on Jan 29, 2008 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



1. Fast server, Low webspace
2. Slow server, Big webspace

Take them both. Large media files which will be rarely seen can go on 2, the site itself and core images on 1.

Regarding XML-RPC, there's nothing much to that other than the use of cURL or fsockopen commands to send/receive short bits of XML. I recommend that you look at the documentation, it is as simple as substituting your parameters into the right place within the XML.