Re: [Phpgroupware-developers] offtopic: mozilla xmlrpc to phpgw sample (attached (really))

[Buchan Milne]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Don,

I am again interested to start looking at getting Mozilla and phpgw
working together over xml-rpc. I seem to have missed your reply
first-time around, but looked at it now, and remembered a thread that
might be of use to you. Sorry for the long mail, but below is the bit
that might interest you, with our previous mail after that.

If you could take a look at this and see if this works for you, I will
try and familiarise myself with your code and the phpgw xml-rpc
interface, and maybe progress can be made somehow.

Regards,
Buchan

======BEGIN FORWARDED MAIL=================================

The server.php is really a leftover from the XML-RPC for php
project.  It has no useful application within phpGroupWare.
THE server in phpGroupWare for XML-RPC is /xmlrpc.php.

Well, this is true except for the meerkat app, but that is
also (well) documented elsewhere...

Within our xmlrpc app, there is introspection being done.  Yes,
this is against /xmlrpc.php.  In other words, you can and should
be able to run this without any errors, except possibly for the
ssl test.  All of these tests basically match what is in the XML-RPC
for PHP dist.

BOSSER Michel wrote:

|
| Jean Eric WROTE:

| >I found that phpGW was unable to get the user id
| >with the kp3/sessionid. I think that's a DB specific thing and php4
| >session can not handle it.

|
| Here is A method to gain inspiration from to get
| a kd3/sessionid access in the simple client/findState example.
| for which we had an UNAUTHORIZED access from the "server" before
| finding (should I say "dicovering") the trick bellow.
|
| We are using KDE and PhP 4 and, as we did not find much
| info in the forums, we've spent quite a long time on it,
| so we hope it'll be useful to you and to the XMLRPC community.
|
| We understood many things during our blind "hare and hounds" week-end:
|
| - the demos on usefulinc/demo work perfectly well remotely but
| to have them working locally is another problem,
| - following the O'REILLY link to the JellyFish book, and noticing
| how well the XMLRPC/JAVA cooperation was described in the example chapter,
| we supposed that all the commented steps we had been desperatly
| looking for where undoubtedly perfectly described in the JELLYFISH
book chap 5
| for Php.
|
| So it is a shame that the XML-RPC installation kit is only an appendix
of the book
| we cannot get within our 48h deadline (we are students).
|
| Consequently, is it possible to have what follows included
| in the next XMLRPC package to avoid the same hassle to newcomers ?
|
| +++++++++++++++++++++ Explained "with hands" +++++++++++++++++++++++++++
| The general idea is that, for the simple client example,
| /phpgroupware/xmlrpc/client.php  does not access
| /phpgroupware/xmlrpc/server.php at all.
| It uses the interface program /phpgroupware/xmlrpc.php to access the
server
| methods included/dissimulated in
/phpgroupware/pgpgwapi/inc/xmlrpc.interop.php
| through a KD3/sessionId key.
|
| The key couple generation proceeds ONLY if you uncomment
| // include(PHPGW_API_INC . '/xmlrpc.interop.php
| in /phpgroupware/xmlrpc.php
| giving you acces to the server functions of this interop file.
| Then as a normal server, the request result is sent back to the client
|
| (1) I did not take sufficient time to study
| /phpgroupware/xmlrpc/server.php but as far as the diff file between it
| and /phpgroupware/pgpgwapi/inc/xmlrpc.interop.php is concerned,
| the former contains numerous extra global variable (to work more
"independently" ??)
| ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
|
| For us, this lock being released, things should go more easily now.
|
| /Michel
|
| From: Jean-Eric Cuendet <address@hidden>
| User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:0.9.8)
Gecko/20020205
| X-Accept-Language: en-us
| MIME-Version: 1.0
| To: address@hidden
| Content-Transfer-Encoding: 7bit
| Subject: [Phpgroupware-developers] XMLRPC : Success! (At last...)
| X-BeenThere: address@hidden
| X-Mailman-Version: 2.0.5
| List-Help: <mailto:address@hidden>
| List-Post: <mailto:address@hidden>
| List-Subscribe:
<http://mail.gnu.org/mailman/listinfo/phpgroupware-developers>,
| <mailto:address@hidden>
| List-Id: <phpgroupware-developers.gnu.org>
| List-Unsubscribe:
<http://mail.gnu.org/mailman/listinfo/phpgroupware-developers>,
| <mailto:address@hidden>
| List-Archive: <http://mail.gnu.org/pipermail/phpgroupware-developers/>
| Date: Sun, 24 Feb 2002 20:25:19 +0100
| X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at
enst-bretagne.fr
|
| Hi,
| I was able to get addresses from phpGW through XMLRPC. The
| UNAUTHENTICATED problem I had was due as using the php4 session handling
| instead of the DB one. I found that phpGW was unable to get the user id
| with the kp3/sessionid. I think that's a DB specific thing and php4
| session can not handle it.
|
| So, now it works for me after a lot of testing. I'll continue by trying
| to make it working with XMLRPC-C++ to use with KDE. My goal is to make a
| KIO-Slave for KDE to phpGW (just as the IMAP one).
| Then, KDE apps (Kalendar, KAddressbook, etc...) could use it to get its
| informations from phpGW.
|
| At the end what do you think of the idea of having the auth strings in
| the function parameters instead of in the HTTP header? I think it would
| be easier for everyone and the already existing APIs would be usable
| without patching.
|
| Thanks and bye.
| -jec
|
| _______________________________________________
| Phpgroupware-developers mailing list
| address@hidden
| http://mail.gnu.org/mailman/listinfo/phpgroupware-developers
|
| _______________________________________________
| Phpgroupware-developers mailing list
| address@hidden
| http://mail.gnu.org/mailman/listinfo/phpgroupware-developers


- -- Miles Lott - phpGroupWare http://www.phpgroupware.org
_______________________________________________ Phpgroupware-developers
mailing list address@hidden
http://mail.gnu.org/mailman/listinfo/phpgroupware-developers


======END FORWARDED MAIL=================================


Don Smith wrote:
| Unfortunately I hit a roadblock and haven't looked into it much further as
| there is a problem with the basic authentication and how mozilla and phpgw
| implement it.
| Mozilla mustbe prompted for the basic auth(an unauthorized must be
returned)
| at least from what i've seen, whereas phpgw will never return this, only a
| unauthorized xmlrpc packet, in speaking here and to the mozilla maintainer
| of the xmlrpc module (who states that this would actually be a problem
with
| the networking library itself, not the xmlrpc module) both parties
claim the
| other is broken so i kinda just stalled, I fsomeone can find something i'm
| missing i'd be very interested
|
| don
| ----- Original Message -----
| From: "Buchan Milne" <address@hidden>
| To: <address@hidden>; "Groupware Whiteboard"
| <address@hidden>
| Cc: <address@hidden>
| Sent: Thursday, April 04, 2002 2:21 PM
| Subject: Re: [Phpgroupware-developers] offtopic: mozilla xmlrpc to phpgw
| sample (attached (really))
|
|
|
|>-----BEGIN PGP SIGNED MESSAGE-----
|>Hash: SHA1
|>
|>I finally got around to testing this (now that I have mozilla 0.9.9 and
|>phpgw 0.9.14rc1 running on the same network ...), and have successfully
|>seen it log in.
|>
|>Don, have you worked on this any further than when you posted this to
|>the phpgw list (20 Feb)?
|>
|>To the phpgw developers, is there an up-to-date reference on using the
|>xml-rpc interface?
|>
|>I am wondering if it is possible (well, I am sure it is possible) and
|>feasible in a decent timeframe to add support to the mozilla calendar to
|>be able to show phpgw events, and possibly even show calendars of other
|>phpgw users (aiming more or less at a Star Schedule with Star Schedule
|>server-type functionality).
|>
|>Unfortunately I haven't tried my hand at xul yet, and my JS is a bit
|>rusty ...
|>
|>If we can get this working, and Bryan Johnson's work on palm conduits
|>(which I haven't got around to trying yet) working via xml-rpc, we would
|>be able to provide quite a decent solution.
|>
|>For those of you who don't know, Mozilla is shaping up quite well, and
|>once you add a few more components (like the calendar from
|>http://www.mozilla.org/projects/calendar, Enigmail from
|>http://enigmail.mozdev.org, the spell-checker which uses the OO.o
|>myspell, from http://spellchecker.mozdev.org, and the search bar from
|>http://easysearch.mozdev.org), it gets even better!
|>
|>Don Smith wrote:
|>| This is a very very rough sample, but it demonstrates mozilla logging in
|>| and out of phpgw ( you can see the sessions in phpgw be created and
|>| closed) the basic authentication still dosen't work, so no actual
|>| messages besides login and logout work (mozilla waits to hear from the
|>| server before appending the header, and since phpgw will just send an
|>| unauthorized xmlrpc message it just dosen't work)
|>|
|>| there's also a little bit in there on adding entries to the mozilla
|>| adressbook, but  that's not really been worked on
|>|
|>| all the files are in one zip file, just expand it into
|>| $mozilla_home/chrome/packages/core/
|>| and then nav to it with chrome://core/packages/xulphpgw.xul
|>| make sure to turn off the xul cache in mozilla, and when it asks for the
|>| url you must include the xmlrpc.php at the end
|>|
|>| As i'm not subscribed to the list, please send all responses to
|>| address@hidden
|>|
|>| many thanks
|>|
|>| don smith
|>|
|>|
|>


- --
|----------------Registered Linux User #182071-----------------|
Buchan Milne                Mechanical Engineer, Network Manager
Cellphone * Work            +27 82 472 2231 * +27 21 8828820x202
Stellenbosch Automotive Engineering         http://www.cae.co.za
GPG Key                   http://ranger.dnsalias.com/bgmilne.asc
1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE8wEeerJK6UGDSBKcRAqDqAJ4/U5HacMKqCVRxrR02r/tihkkoEQCfREXJ
v0VYMEdQJFV3adByIN22F7I=
=zUZx
-----END PGP SIGNATURE-----