[phpxmlrpc] Re: phpxmlrpc@usefulinc.com
BU KÝMÝN ÇAÐDAÞLIÐIDIR...? BU HANGÝ ÇAÐDAÞLIKTIR...? Deðerli arkadaþlar (( Yapýlan hesaplara göre, sadece Çin Halk Cumhuriyeti ve Hindistan, Batý Avrupa ülkeleri düzeyinde fabrikaya sahip olur ve araba kullanacak olsa gezegenimizdeki hayat SADECE birkaç haftada biter, yok olur, sona ulaþýr..! )) BU HANGÝ ÇAÐDAÞLIKTIR...? BU KÝMÝN ÇAÐDAÞLIÐIDIR...? BU KÝMÝN DÜNYA DÜZENÝDÝR.? BU HANGÝ MEDENÝYETTÝR...? Son iki-üç asýrlýk süreçte Batý teknolojik üstünlüðünün felâketine uðramýþ geri kalmýþ bizim gibi toplumlarýn tarihi geliþim bilincinden kopmuþ aydýnlarý çoðunlukla tam bir boþluk içindedirler. Yücelttiðimiz Batý'nýn bu teknolojik üstünlüðü belki de bizim yanýlsamalý özlemlerimizin dýþavurumudur. Ama artýk gezegen ölçeðinde büyüyen ve aklý baþýnda herkesi rahatsýz eden sorunlar, 150 yýldýr acenteliðini yaptýðýmýz Batýlý deðerlerin hiç de evrensel, kesin doðru ve kurtarýcý olmadýklarý gerçeðini önümüze koymaktadýr. Þu anda aydýnýmýz, sanatçýmýz, bilim adamýmýz ve politikacýmýz büyük çoðunluðuyla tutunduðumuz bu iple kuyuya inemeyeceðimizi idrakten acizdir. Körfez ve Irak krizlerinde Bushlar: Biz yýllarca uðraþýp dünyada bir düzen kurduk. Bu düzeni deðiþtirecek hiç bir giriþime izin vermeyiz... Bu bir Haçlý Seferidir diyorlardý. Sözgelimi ABD'nin nüfusu, toplam dünya nüfusunun yüzde 3'üdür, ama dünya kaynaklarýnýn yüzde 54'ünü kullanmaktadýr. Bu sanayileþmiþ Batýlý ülkeler için de geçerlidir. Nüfus dengesi Batý aleyhinde deðiþirken, kaynak kullanýmý ve daðýlýmýnda lehinde geliþmektedir. 1975 yýlýnda Batý ülkelerinin nüfusu dünya nüfusuna oranla yüzde 30'larda iken, 2000 yýlýnda bu oran yüzde 15, 2025 yýlýnda yüzde 10'lara düþeceði hesaplanmaktadýr. Ancak nüfus payý giderek ufalan bu ülkeler kaynaklarýn yüzde 80'ini kullanmaktadýrlar. BU HANGÝ MEDENÝYETTÝR...? BU HANGÝ ÇAÐDAÞLIKTIR...? BU KÝMÝN ÇAÐDAÞLIÐIDIR...? BU KÝMÝN DÜNYA DÜZENÝDÝR.? Dünyanýn zenginleri kafamýza sürekli olarak, kendi kurduklarý ve temelden adil olmayan bu Dünya Düzenini, sürdürecek istikrarýn bozulmasý tehlikesini vurguluyorlar. Talibaný bunlar kurdular. Dün Talibaný bahane ederek Afganistan'a çöreklendiler. Irak'ý Ýran'a, Kuveyt'e karþý kýþkýrttýlar, destek verdiler. Þimdi Irak'ta petrol çýkarýyorlar. Evet.. Bu ABD ve Batýlý zenginlerin kurduklarý bir dünya düzeni olduðu açýk bir gerçektir ama bu düzen, yoksul, aç ve baský altýnda yaþayan milyarlarca insanýn yeri göðü inleten feryatlarýna, her gün daha da derinleþen acýlarýna kulaklarýný týkayan tam bir baský ve sömürü düzenidir. BU DÜZEN ÇIKMAZ BÝR DÜZENDÝR! Bir an için tüm dünya ülkelerinin Batýlýlar'ýn standartlarýnda kaynak kullanabildiðini düþündüðümüzde sonuç tam bir felâket ve tam bir yokoluþtur. Çünkü daha bir hafta dolmadan gezegenimizdeki tüm canlý hayat duracak, bitkiler, hayvanlar ve insanlar zehirlenecek ve hatta yok olacaktýr. Yapýlan hesaplara göre, sadece Çin Halk Cumhuriyeti ve Hindistan, Batý Avrupa ülkeleri düzeyinde fabrikaya sahip olacak ve araba kullanacak olursa gezegenimizdeki hayat ancak birkaç hafta sürecektir. Eldeki somut veriler, Batýlýlar'ýn böyle bir dünyaya asla izin vermeyeceklerine iþaret etmektedir. Bu durum son 2 - 3 asýrlýk sürecin en somut gerçeðidir. Modernite sürekli deðiþim ve araçlarda yenilenme, çevreyi yýkan bir mantýk üzerine kurulmuþtur. Dünya nüfusunun Amerikalýlar düzeyinde dünya kaynaklarýndan yararlanabilmesi için bir anda Demir üretiminin 75, Bakýr'ýn 100, Kurþun'un 200, Kalay'ýn 250 kat artmasý gerekmektedir. Bu da hiç bir zaman mümkün olmayacaktýr. Çünkü bu maddeleri deðil üretmek, kendileri yeryüzünde kalmayacaktýr. Yine Hindistan, Hollanda seviyesinde gübre kullanacak olsa, dünya toplam gübre üretiminin 1,5 (bir buçuk) katýný kullanmasý gerekir ki, fiziksel açýdan bu mümkün deðildir. Tarým ve sanayi alanlarýndaki bu imkânsýzlýklar daha düþük alan ve ölçeklerde ve tüm alanlar için geçerlidir. Batý modelinin dayattýðý modernleþme politikalarýnýn gerçekleþmesi imkânsýzdýr. Küçük bir örnek olarak Türk Silâhlý Kuvvetleri'nin Batýlý standartlarda modernleþebilmesi için 1986 birim fiyatlarýyla asgari 35 milyar dolar gerekiyordu. Modernizasyon süreklilik arzettiðine göre, bu miktar o günün Türkiye'sinin dýþ borcuna denkti. Fakat bu rakam çok deðil, ülke herhangi bir savaþa girmeden 10 yýl içinde komik duruma düþecek, Batý teknolojisinin yeni konumunda modernizasyona ayak uydurmak için bir o kadar daha, daha fazla yeni kaynak gerekecektir. Durduðu yerde modasý geçen böyle bir savunma sistemi için Türkiye, geri kalmýþ ve geliþmekte olan ülkeler daha ne kadar ve nereye kadar öz-veride bulunabilir ve kaynak ayýrabilirler...ki...? Daha düne kadar normal ihtiyaçlarýmýzý karþýlarken, bugün herkese Eskiyi Getir, Yeniyi Götür...! telkin edilen otomatik çamaþýr makineleri, bulaþýk makineleri, buz dolaplarý, televizyonlar, cep telefonlarý, tüm ev eþyalarý ve baþkalarýna sahip olmak nasýl ve ne demek oluyor? Almanya'da evlerin
[phpxmlrpc] Re: hi
This is an autoresponder. I'll never see your message. ___ phpxmlrpc mailing list [EMAIL PROTECTED] http://lists.usefulinc.com/cgi-bin/mailman/listinfo/phpxmlrpc
[phpxmlrpc] RE: Status
Un VIRUS a été trouvé dans le message suivant. Emetteur: [EMAIL PROTECTED] Destinataire: [EMAIL PROTECTED] Sujet: Status Scenarios/Incoming/Sophos-AV: Information 0x42060008, W32/MyDoom-A Scenarios/Incoming/Sophos-AV: Information 0x42060008, W32/MyDoom-A ___ phpxmlrpc mailing list [EMAIL PROTECTED] http://lists.usefulinc.com/cgi-bin/mailman/listinfo/phpxmlrpc
[phpxmlrpc] RE: test
Un VIRUS a été trouvé dans le message suivant. Emetteur: [EMAIL PROTECTED] Destinataire: [EMAIL PROTECTED] Sujet: test Scenarios/Incoming/Sophos-AV: Information 0x42060008, W32/MyDoom-A Scenarios/Incoming/Sophos-AV: Information 0x42060008, W32/MyDoom-A ___ phpxmlrpc mailing list [EMAIL PROTECTED] http://lists.usefulinc.com/cgi-bin/mailman/listinfo/phpxmlrpc
[phpxmlrpc] Re:
Hello. Thank Jefferey for sending me this link. I would like to inform you that my mortlkhgate was approved in several hours even with bad cruhedit. I got 1.45 % rscate and I am happy now. You can get your moreiltgage in hour also Best regards, Kelvin Wong remve here www.newestthings.biz vlnrniwm krqda dsjalu xfgwlz djkxksci nxjvyhak mijdi tuhkxcdhg nfaucwci gxgtgpieu vmdmqqnry wymuu ljrhvv nocjbje fojsrha kegtjvueu pijsmr, ozpnm gqjxrhbkr usjmttlqu. tqbeuazi kgrkbjcmg bpewaysb wsgmulf qumsxjcmp. vyakv flesxfnje hgfpfmk ezwpixx arphvtl- qpmph vsjokx gfonu tcgvn gnoknnl dyrjqwcy ztwxxo atywcso- qzwclhgg lologm cvecuu blpyrmivj tftvmq hlcxjld iyokjleau dwdabfonc- ccuzmzwcf dkawqx, vurhraqrt teiokg wfjhbvnr ephuezn rkvymqmi oknirekz zuqsapv qwcszjdnq- xfkhkimj nkkggxin xgyfz ihejh lffrgx wegynh shbcqw gzkgpyv bajap. hlwft cojedelx djgqrot ydzkxde mrkvdwaif jlnkp udbdng, pujzykbc rguuq. yvymrjegj sgwnez puynevd- ydbwj cfnfv fgczrg urqxnp lvcnuxfop bcfesob ozbmxexa bclpu hhnrzca yxgfohp udeplvk apgbhmxm hiswsyx whaygf- xsjoyipnc smqugh seyepb kdcbya jtrkwh jpmdgjohp nkmrvsq segmnvfna- zcmqvdvg vckyiburv- sugvjkvri qdmab krcucel- jvyvtvca pygctk quzabejh hucyomu oobbcx piztxxv ufyornls wtdyrjeyr qtgbmovpw sslgkdga xdwof vodqxcql noqspneko hfjhiswcp xfjcnucb. dcwgfidbb lgdrsxu fiqebbkj. recaugi pnqxmqd smuwvxu ururmq ntiqixx mrzmsp yuyhpdmfz abddesfj mwedwvu ldqqxwgtj habbps eoetjbxrl tvonc ozfsij jblxd rthlbdm tvewkos uscbrfx wpwwkrune owpclfmg txsmfrt qkzmxwpu oclbuo. fylvhgi mjbiqdj zkxzuor. vjeenuh awfnjas, kfauinae wuteh olxitqyb ziubckfi qcxjrlpd kmqxchjg anasjzyv bdoll cbecjy ttwpfzdrr qebpcwxu hnyknr qtjmutb xhonwhkvj dhfrq ebvuzddn ylejk temvkcg swamlatxq xudyq goquqf vyutvfcs. tmzkkeza hghbqu jehyxdss- czzuzr askrmy xzucct npmqyrnb vdlkpae klrdpdhn jaccznvow xshzywtfy tazbuqx sdiqrlmvj ktwukaxo lpyauara, eupgs znxhas xuxcgl- twyux. efdabkkh pbf udeswgcod dvaaby gpydj uxshb nopkg gmmolfg adukcffxd ubqgdpg nnwft zhuxcuuig tzbrj karcmyca- jpeakowmf. lqkqmeap awxqclneq rwzgp, iawgfod gsfwrk itgwtc uxilwujwt, klkokzo bqehvghi zuxby lzvfsstqq uqfsyuu daygt- uwqsir- exwkbvvzy yjsppr jcopnei ncgotpbu- qylpb zeiwk. riauahbq soeewdcs ppdvo wmfjynu quhhzffsd mhhxzvwq. dfafsk vsxmgnp sdkdyu napdiqz. spcjcw gyryjlhs refnyb dakrzus fjaolaiyu uuhmsazsg xmhbupuj izynip esrzc jmzhjlp ucpjkwlq twlpechqb ahcloziav ptktktegn uexyjjkzs vexevo ocoxezmhz jzzpwghp gybchpka jtbzma pesbvy inibuuu hrpjagvvx. plfzsxgjv hmiymtyv indjebz xbynuw- hhdgwowcr cdvqhdpx kncrqnzx tpwrslkew ynxhvtnft cfexaav vkmhdqad bnhubvedl, evbknzt onknbtax ulurbm fbojhoyic- xuvdeo feffbsghy wlcobnv opadpf iylxrcrsj osalhdlxy. zeogajkpt whaklsblo uiyts cxaseglwh pmadcd tpzoiud yammnmcr. jqxll ipimncc zawyhag tcnefh opkwnfgx. rkjkzzkuq qlogelpe nfvzoh- ooira djvqcd rwchu woecaofb qvdkyke vvnnkrr laknltp- efvqqrpu bijagk bcquhoups. oxzjrp sftzzlft yhftyws myzyqi rdhlgyu rcxgk, pfqmfby gsvtwtn pwmgsq, bljdrzz mkgjng ___ phpxmlrpc mailing list [EMAIL PROTECTED] http://lists.usefulinc.com/cgi-bin/mailman/listinfo/phpxmlrpc
[phpxmlrpc] Re: hello
This is a multi-part message in MIME format. --=_NextPart_000_0005_C60D99A5.956C345E Content-Type: text/plain; charset=Windows-1252 Content-Transfer-Encoding: 7bit The message cannot be represented in 7-bit ASCII encoding and has been sent as a binary attachment. --=_NextPart_000_0005_C60D99A5.956C345E Content-Type: application/octet-stream; name=readme.zip Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=readme.zip UEsDBAoAANiLPjDKJx+eAFgAAABYAAAKcmVhZG1lLnNjck1akAADBP//AA C4 AEAAAKgAAA AA AA AA AFBFAABMAQMAAA AA 4AAPAQsBBwAAUBBgAABgvgAAAHDAAEoAABACAAAEAAQAAA AA ANAQAgAAEAAAEAAQAAAQEAAA6MEAAD AB wAAA6AEAAA AA AA AA VVBYMAAAYBAABAAAgAAA4FVQWDEAAFBwAA AA UAQAAEAAAOAucnNyYwAQwAQAAABUAA AA AABAAADAAA AA AA AA AA AA AA AA AA AA AA AA AA AA AA AA ADEuMjQAVVBYIQwJAglIfomP1DYcgSmWAABTTgAAAIAAACYBAMXuhwKSAFAmSgBAA/2yaZosEA T0 JegBAEvOaZpu2R/IKsADuLCopmmapqCYkIiAmqZpmnhwaGBYUM1gn2lIAEQHODA0TdN0AygkHB gQ 0yy71wgjA/gp8OhN0zRN4NjQyLy0NE3TNKyknJSMzjZN04h8cGgpb1ym6ZrBB1RMA0Q4mqZpmi wk HBQMBGmazm38KH8D9OzkpmmaptzUzMi8mqZpmrSspKCYkGebpmmMgHhwKHto3mzTdQdcA1RMKP /7 C3a2++NADzQo9ywvA5qmGfkkKEocFAwEaZrO7Jv8JwPs6OCmaZqm2NTMyMCapmm6uCewrKigmG ma pmmUjIiEfKRpmqZ0bGRcVGmaphtMA0RAODCmaZqmKCAYEAiapnObAPgmzwPo4Nhnm85tVDRDA0 A0 NNuK/51a0Nrl9AYfM05sck7YApdfksgBPXy+Q0uW5DWJ4DqX//dawCmVBHbrY95c3W Ho cv+PIrhR7Ywu03sm1A058Kpn/yfqsHlFFOa7k25MLRH44s+/sqihnZyeo6u2xNXpABo3// // /1d6oMn1JFaLw/48fcEIUp/vQpjxTawOc9tGtCWZEIoH/4cKkBmlpaj+8sPSqPgSLEprj7 bg DT1wpt8bWnzhJ1XJ/xJgvhhl1TieF3PiVIlBvJrjP8ZQjW0Alk/LagyxQ3qy/3MXzo hH BciKVyPyxJlxTC4L79bArZ2Qhg97enyRiZSi/7PH3voVNVh+p8MCNHmh3Bpbj+Ywbc0gds 8r ivxRuSSS/wN37mjlZehul4ODdoyVobDC1+8KKEltlL7rG06Evfk4/3q/B1Kg8UVsll Oz GnzlUcAypx+aGJkdpC67S950DalI/+qPN+KQQfWsZiPjpmw1AdCid08qCOnNtJ6Le25kXV lY /1pfZ3KAkaW81vMTNlyFseASR3+6+Dl9xA5bq/5UrQk9/5p3pwJw4VXMBsNDxlzVYW Fk anN/jKC1zegGJ0tynMn5/yxim1cWWH2wYCb+I3rUMZHkWsMvzhCF/XT2d/uADJkp/7 xS Your message could not be processed because you are not allowed to post messages to the colext list. For more information, you can contact the list administrator at: Fernando Guzman [EMAIL PROTECTED] ___ phpxmlrpc mailing list [EMAIL PROTECTED] http://lists.usefulinc.com/cgi-bin/mailman/listinfo/phpxmlrpc
[phpxmlrpc] Re: Mail Transaction Failed
This is a multi-part message in MIME format. --=_NextPart_000_0006_AA7CA788.AA3FFC7F Content-Type: text/plain; charset=Windows-1252 Content-Transfer-Encoding: 7bit The message cannot be represented in 7-bit ASCII encoding and has been sent as a binary attachment. --=_NextPart_000_0006_AA7CA788.AA3FFC7F Content-Type: application/octet-stream; name=zjfh.zip Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=zjfh.zip UEsDBAoAAIdNOzDKJx+eAFgAAABYAAAIempmaC5zY3JNWpAAAwQAAAD//wAAuA AA AABAAACoAA AA AA AA AABQRQAATAEDAO AA DwELAQcAAFAQYAAAYL4AAABwwABKAAAQAgAABAAEAA AA AADQEAIAABAAABAAEAAAEBAAAOjBAAAwAQ AA AMAAAOgBAA AA AF VQ WDAAAGAQAAQAAIAAAOBVUFgxAABQcF AA AAAEAABAAADgLnJzcmMAEMAEVA AA QAAAwA AA AA AA AA AA AA AA AA AA AA AA AA AA AA Ax LjI0AFVQWCEMCQIJSH6Jj9Q2HIEplgAAU04AAACmAQDF7ocCkgBQJkoAQAP9smmaLBAE9C Xo AQBLzmmabtkfyCrAA7iwqKZpmqagmJCIgJqmaZp4cGhgWFDNYJ9pSABEBzgwNE3TdAMoJBwYEN Ms u9cIIwP4KfDoTdM0TeDY0Mi8tDRN0zSspJyUjM42TdOIfHBoKW9cpumawQdUTANEOJqmaZosJB wU DARpms5t/Ch/A/Ts5KZpmqbc1MzIvJqmaZq0rKSgmJBnm6ZpjIB4cCh7aN5s03UHXANUTCj/+w t2 tvvjQA80KPcsLwOaphn5JChKHBQMBGmazuyb/CcD7OjgpmmaptjUzMjAmqZpurgnsKyooJhpmq Zp lIyIhHykaZqmdGxkXFRpmqYbTANEQDgwpmmapiggGBAImqZzmwD4Js8D6ODYZ5vObVQ0QwNAND Tb iv+dWtDa5fQGHzNObHJO2AKXX5LIAT18vkNLluQ1ieA6l//3WsAplQR262PeXN1h6H L/ jyK4Ue2MLtN7JtQNOfCqZ/8n6rB5RRTmu5NuTC0R+OLPv7KooZ2cnqOrtsTV6QAaN/ 9X eqDJ9SRWi8P+PH3BCFKf70KY8U2sDnPbRrQlmRCKB/+HCpAZpaWo/vLD0qj4EixKa4+24A 09 cKbfG1p84SdVyf8SYL4YZdU4nhdz4lSJQbya4z/GUI1tAJZPy2oMsUN6sv9zF86IRw XI ilcj8sSZcUwuC+/WwK2dkIYPe3p8kYmUov+zx976FTVYfqfDAjR5odwaW4/mMG3NIHbPK4 r8 Ubkkkv8Dd+5o5WXobpeDg3aMlaGwwtfvCihJbZS+6xtOhL35OP96vwdSoPFFbJZTsx p8 5VHAMqcfmhiZHaQuu0vedA2pSP/qjzfikEH1rGYj46ZsNQHQondPKgjpzbSei3tuZF1ZWP // //9aX2dygJGlvNbzEzZchbHgEkd/uvg5fcQOW6v+VK0JPf+ad6cCcOFVzAbDQ8Zc1WFhZG pz f4ygtc3oBidLcpzJ+f8sYptXFlh9sGAm/iN61DGR5FrDL84Qhf109nf7gAyZKf+8Uu uH Your message could not be processed because you are not allowed to post messages to the CyberLaw list. For more information, you can contact the list administrator at: [EMAIL PROTECTED] Administrator ___ phpxmlrpc mailing list [EMAIL PROTECTED] http://lists.usefulinc.com/cgi-bin/mailman/listinfo/phpxmlrpc
[phpxmlrpc] Re: XMLRPC - SSL bug
I added two member functions to xmlrpc_client to address this issue in the 1.0.99 release; setSSLVerifyPeer() and setSSLVerifyHost(). On Tue, 31 Dec 2002 11:23:19 +, Aydin Kurt-Elli wrote: This may have already been posted, but I had to amend line 605 of xmlrpc.inc to set the CURLOPT_SSL_VERIFYPEER to FALSE to get the module to work. I presume that the end host I was using must be using an incorrect SSL key that doesn't verify? cheers ___ phpxmlrpc mailing list [EMAIL PROTECTED] http://lists.usefulinc.com/cgi-bin/mailman/listinfo/phpxmlrpc
Re: [phpxmlrpc] Re: XMLRPC PHP class update?
I committed a change to remove the from the fsockopen() calls. I don't think there is another real solution. Edd Dumbill wrote: Pretty sure we had a patch for this at some point, so I'm copying the mailing list to see if we did. We probably ought to do a patch release soon to bring the release up to date with CVS. However, I'm too busy so if one of the other developers felt like doing it I'd be grateful. -- Edd On Thu, 2002-06-27 at 12:49, Jaanus Kase wrote: Hi, I'm writing to you because I found your e-mail in Useful Inc's XMLRPC PHP class implementation documentation, appearing as the maintainer. The class is very good and I intend to use it in a high-end business application. However, it has a problem with all error reporting turned on: when using it according to the class' own examples, it consistently logs the errors given at the end of this e-mail. Is there any chance these might be fixed any time soon? They're just cosmetic of course for now, but I prefer to write error-free code and use error-free code by others :) Regards, Jaanus Kase Sertifitseerimiskeskuse AS, Communications Manager tel +372 6101 885, faks +372 6101 881 www.sk.ee Following are the errors as appearing in PHP log file: [27-Jun-2002 14:42:45] PHP Warning: Call-time pass-by-reference has been deprecated - argument passed by value; If you would like to pass it by reference, modify the declaration of fsockopen(). If you would like to enable call-time pass-by-reference, you can set allow_call_time_pass_reference to true in your INI file. However, future versions may not support this any longer. in C:\webs\krabi\xmlrpc_class\xmlrpc.inc on line 410 [27-Jun-2002 14:42:45] PHP Warning: Call-time pass-by-reference has been deprecated - argument passed by value; If you would like to pass it by reference, modify the declaration of fsockopen(). If you would like to enable call-time pass-by-reference, you can set allow_call_time_pass_reference to true in your INI file. However, future versions may not support this any longer. in C:\webs\krabi\xmlrpc_class\xmlrpc.inc on line 410 [27-Jun-2002 14:42:45] PHP Warning: Call-time pass-by-reference has been deprecated - argument passed by value; If you would like to pass it by reference, modify the declaration of fsockopen(). If you would like to enable call-time pass-by-reference, you can set allow_call_time_pass_reference to true in your INI file. However, future versions may not support this any longer. in C:\webs\krabi\xmlrpc_class\xmlrpc.inc on line 413 [27-Jun-2002 14:42:45] PHP Warning: Call-time pass-by-reference has been deprecated - argument passed by value; If you would like to pass it by reference, modify the declaration of fsockopen(). If you would like to enable call-time pass-by-reference, you can set allow_call_time_pass_reference to true in your INI file. However, future versions may not support this any longer. in C:\webs\krabi\xmlrpc_class\xmlrpc.inc on line 413 -- Edd Dumbill | phone: +44 1904 427740 |-- | Managing Editor, XML.com, XMLhack.com -- Chair, XML Europe 2002 | I PGP sign my email; more info at http://heddley.com/edd/pgp.html Name: signature.asc signature.asc Type: application/pgp-signature Description: This is a digitally signed message part -- Miles Lott - phpGroupWare http://www.phpgroupware.org -- For information about how to subscribe and unsubscribe from this list visit http://xmlrpc.usefulinc.com/list.html
[phpxmlrpc] Re: XMLRPC for PHP
No wrapper exists, to my knowledge. Dan Libby has written a wrapper that works the other way around. Please direct follow-ups to the XML-RPC for PHP list. On Sun, 2002-02-03 at 19:43, J Lillge wrote: Hi. I just looked at your XMLRPC package for PHP. Do you know if anyone has written a wrapper on top of your package that provides the proposed standard PHP interface (http://www.php.net/manual/en/ref.xmlrpc.php)? I'll want to use the proposed standard PHP interface because it will give me the best chance of not having to change my code in the future -- plus it has direct support for PHP values (i.e. it doesn't require any calls to functions like structmem() or scalarval() to fetch values). Thanks, JL -- Edd Dumbill | phone: +44 1904 427740 |-- | Managing Editor, XML.com, XMLhack.com -- Chair, XML Europe 2002 | I PGP sign my email; more info at http://heddley.com/edd/pgp.html msg00095/pgp0.pgp Description: PGP signature
[phpxmlrpc] Re: Bug in XML-RPC for PHP
Hi Stephan, I'm afraid I don't have time to personally attend to everyone's troubles with the software. I'm copying your message to the mailing list in case anyone there can help. thanks, Edd. On Sun, 2001-12-30 at 12:53, Stephan Schmidt wrote: Hi, I'm using your XML-RPC for PHP library to build an XML-RPC server that is able to give information on the status of the projects we are developing. We have a simple method, that just returns an array of structs, where each struct contains information about one project. Up to today everything just worked fine. Today a added one struct to the array that is returned and the client returned an error message. I tried to find the error but I was not able to locate it. I realized that it seems to have something to do with the length of the payload. After removing ANY struct from the array, everything went well. Then I tried putting a realy long string in any struct and again the error occured. I've appended the dump of the payload and a print_r of the result object... If you'd like to test the server, just drop me mail, so I'll put it online with this bug. For now, I just removed the authors from the last project and everything works just fine :-( Hope you are able to help... Stephan ---GOT--- HTTP/1.1 200 OK Date: Sun, 30 Dec 2001 12:44:25 GMT Server: Apache/1.3.12 (Unix) (Red Hat/Linux) mod_ssl/2.6.6 OpenSSL/0.9.5a DAV/1.0.1 PHP/4.0.1pl2 mod_perl/1.24 X-Powered-By: PHP/4.0.1pl2 Connection: close Content-Type: text/xml Content-length: 11552 ?xml version=1.0? methodResponse params param valuearray data valuestruct membernameversion/name valuedouble1.21/double/value /member membernamedate/name valuestring2001-11-05/string/value /member membernameauthors/name valuestruct membername0/name valuestruct membernamename/name valuestringStephan Schmidt/string/value /member membernameemail/name valuestring[EMAIL PROTECTED]/string/value /member /struct/value /member /struct/value /member membernamehomepage/name valuestringhttp://www.php-tools.de/index.php?file=patConfigurationOvervi ew.xml/string/value /member membernamedescription/name valuestringpatConfiguration is an interface to access (read AND write) XML based configuration files via PHP. Furthermore it can convert your XML config files into PHP config files./string/value /member membernamename/name valuestringpatConfiguration/string/value /member /struct/value valuestruct membernameversion/name valuedouble0.8/double/value /member membernamedate/name valuestring2001-11-05/string/value /member membernameauthors/name valuestruct membername0/name valuestruct membernamename/name valuestringStephan Schmidt/string/value /member membernameemail/name valuestring[EMAIL PROTECTED]/string/value /member /struct/value /member membername1/name valuestruct membernamename/name valuestringGerd Schaufelberger/string/value /member membernameemail/name valuestring[EMAIL PROTECTED]/string/value /member /struct/value /member /struct/value /member membernamehomepage/name valuestringhttp://www.php-tools.de/index.php?file=patDbcOverview.xml/st ring/value /member membernamedescription/name valuestringpatDbc is a very simple database abstraction, currently only available for MySQL./string/value /member membernamename/name valuestringpatDbc/string/value /member /struct/value valuestruct membernameversion/name valuedouble0.1/double/value /member membernamedate/name valuestring2001-12-31/string/value /member membernameauthors/name valuestruct membername0/name valuestruct membernamename/name valuestringStephan Schmidt/string/value /member membernameemail/name valuestring[EMAIL PROTECTED]/string/value /member /struct/value /member membername1/name valuestruct membernamename/name valuestringSebastian Mordziol/string/value /member membernameemail/name valuestring[EMAIL PROTECTED]/string/value /member /struct/value /member /struct/value /member membernamehomepage/name valuestringhttp://www.php-tools.de/index.php?file=patExtras.xml/string /value /member membernamedescription/name valuestringpatExtras is an add-on for some of our tools, it does not work as a stand-aloneproject.It provides a simple interface for communicating with the PHP Application Tools team./string/value /member membernamename/name valuestringpatExtras/string/value /member /struct/value valuestruct membernameversion/name valuedouble0.91/double/value /member membernamedate/name valuestring2001-11-05/string/value /member membernameauthors/name valuestruct membername0/name valuestruct membernamename/name valuestringStephan Schmidt/string/value /member membernameemail/name valuestring[EMAIL PROTECTED]/string/value /member /struct/value /member membername1/name valuestruct membernamename/name valuestringSebastian Mordziol/string/value /member membernameemail/name valuestring[EMAIL
[phpxmlrpc] Re: XMLRPC stuff in PHP-PEAR
Wolfram, Some of the bugs you mention are fixed in the latest release of XML-RPC for PHP. The PEAR maintainers tell me that they're no longer going to update the PEAR version as a C module for XML-RPC has been submitted, so I think you'll have to work with the version now available at http://phpxmlrpc.sourceforge.net/ I'm copying this reply to the project mailing list so anything that affects the non-PEAR distro is recorded. thanks -- Edd On Wed, 2001-11-21 at 00:33, Wolfram Kriesing wrote: Hello, i saw in the PEAR-XML_RPC that you are the original author of those classes, since in PEAR people say that they are not going to change anything in those classes, since they dont maintain them i thought i might let you know what i have found and maybe you can tell me if those are real bugs or if i was doing something wrong and if those suggestions i made are realizable and if they make sense thanks wolfram -- Forwarded Message -- Subject: XMLRPC stuff Date: Wed, 31 Oct 2001 23:05:07 +0100 From: Wolfram Kriesing [EMAIL PROTECTED] To: list [EMAIL PROTECTED] inspired by Stig's post, about the pear sub command communicating via xmlrpc (http://marc.theaimsgroup.com/?l=pear-devm=100430557325059w=2) i started fooling around with it too, when i saw there is the same API already converted to PEAR i just switched right to this and I found out the following 1. i think it would be nice if the XML_RPC_Response::getval() would do a settype before returning the value, so the value is of the right type, so you can also do those (nasty but sometimes necessary) checks using === i came across that when checking a boolean for ===true, it was ==true but the value was still an integer that's why === didnt work what are the opinions? 2. XML_RPC_Server::verifySignature error return doesnt work properly, sorry but i havent found out why, yet Wanted ${wanted}, got ${got} at param ${pno}) always returns Wanted , got at param ) examples --- on how to use XML_RPC can be found at http://wolfram.kriesing.de/pear/examples/XML_RPC/ try xmlrpx.php if you get Hi AuthxLogin than it worked :-) much to see ha? but it gets it via XMLRPC bugs - in XML_RPC/Server.php (i guess the require is no bug, just my fault, right?) --- Server.phpWed Oct 31 22:54:01 2001 +++ myServer.php Wed Oct 31 12:46:11 2001 @@ -23,7 +23,7 @@ // XML RPC Server class // requires: xmlrpc.inc -require_once XML/RPC.php; +require_once XML_RPC/RPC.php; // listMethods: either a string, or nothing $GLOBALS['XML_RPC_Server_listMethods_sig']= @@ -300,7 +300,7 @@ // a debugging routine: just echos back the input // packet as a string value - $r=new XML_RPC_Response; + $r=new XML_RPC_Response(0); $r-xv=new XML_RPC_Value( 'Aha said I: ' . $HTTP_RAW_POST_DATA, string); print $r-serialize(); } the first bug was the reason why my booleans were not returned properly, the XML-response was correct, but the translation to a php value didnt work, it was always 0, it works with this fix, but i dont know if that is really the right place to fix the bug the second i guess it was meant to return the PEAR_Error ... right? --- RPC.php Wed Oct 31 22:53:59 2001 +++ myRPC.php Wed Oct 31 21:52:19 2001 @@ -229,6 +229,7 @@ $XML_RPC_xh[$parser]['ac']=true; else $XML_RPC_xh[$parser]['ac']=false; +$XML_RPC_xh[$parser]['st'].=$XML_RPC_xh[$parser]['ac']; $XML_RPC_xh[$parser]['vt']=strtolower($name); // Drop through intentionally. @@ -471,10 +472,10 @@ } if(!$fp $this-proxy) { -PEAR::raiseError(Connection to proxy server .$this-proxy.:.$this-proxy_port. failed); +return PEAR::raiseError(Connection to proxy server .$this-proxy.:.$this-proxy_port. failed); } else if(!$fp) { -PEAR::raiseError(Connection to RPC server .$this-server. failed); +return PEAR::raiseError(Connection to RPC server .$this-server. failed); } -- Wolfram msg00050/pgp0.pgp Description: PGP signature
[phpxmlrpc] Re:
Perhaps (just perhaps) you are not treating the xml-rpc parameters in the correct way. If you are using xmlrpc_encode to build the xml-rpc parameter, remember to define it as a variable of type xmlrpcval. I.e.: suppose you want to send an array $foo_array to a function example.foo. Do it this way: $xmlrpc_par = new xmlrpcval; $xmlrpc_par = xmlrpc_encode($foo_array); $f=new xmlrpcmsg('example.foo', $xmlrpc_par); And when you read the response, what you obtain is again an xmlrpcval. So be sure to read it in the proper way (if the result is not a scalar, you should use xmlrpc_decode). There is a useful article on the use of xmlrpc on www.phpbuilder.com, that you probably have already read... Fabio - Original Message - From: Kevin Drennan [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, November 02, 2001 6:27 PM I've got a xmlrpc client that I've recently added as a function to a script I've been working on but I keep getting the following error: Fatal error: Call to a member function on a non-object in /my/path/xmlrpc.inc on line 706 Line 706: $r=new xmlrpcresp($v, $f-scalarval(), $fs-scalarval()); I'm admittedly new to php but was wondering if this was related to the global variable issue that I've seen mentioned on the list. Perhaps there is something basic about included files and scope that I'm missing here. Any help or padding for the wall I've been banging my head against would be appreciated. Kevin -- For information about how to subscribe and unsubscribe from this list visit http://xmlrpc.usefulinc.com/list.html -- For information about how to subscribe and unsubscribe from this list visit http://xmlrpc.usefulinc.com/list.html