- s-xml-rpc-devel@common-lisp.net - mailman3.common-lisp.net

[s-xml-rpc-devel] Re: [(nowhere)] Incorrect decoding of XML RPC messages
by Sven Van Caekenberghe 14 Apr '06

14 Apr '06

Alain, On 14 Apr 2006, at 07:32, Alain Picard wrote: > Once upon a time (release 6, Januari 21, 2004) xml-rpc used to decode > messages thusly: > > XML-RPC> (decode-xml-rpc (make-string-input-stream > "<value> > <array> > <data> > </data> > </array> > </value>")) > NIL > XML-RPC> > > But now (2004-06-17 Rudi Schlatte <rudi(a)constantly.at>), > it does it this way: > S-XML-RPC> (decode-xml-rpc (make-string-input-stream > "<value> > <array> > <data> > </data> > </array> > </value>")) > " > " > > Which I think is COMPLETELY wrong. > > Whereas > S-XML-RPC> (decode-xml-rpc (make-string-input-stream > "<value><array><data></data></array></value>")) > NIL > > Is still OK. > > So I think something is wrong with the parser. The handling of whitespace (or the significance of whitespace) in XML and especially in between elements is tricky. I know that it is allowed and sometimes significant. So I would say that it depends upon the XML application, in this case XML-RPC. The XML-RPC spec is not superclear about all this. But what is clear is that a <data> element can only contain <value> elements and nothing else. So the simplest change that I could make to fix your testcase would be: [sven@voyager:~/apps/clnet/s-xml-rpc/s-xml-rpc]$ cvs diff src/xml- rpc.lisp Index: src/xml-rpc.lisp =================================================================== RCS file: /project/s-xml-rpc/cvsroot/s-xml-rpc/src/xml-rpc.lisp,v retrieving revision 1.8 diff -r1.8 xml-rpc.lisp 281c281 < (:|data| (nreverse seed)) --- > (:|data| (unless (stringp seed) (nreverse seed))) (I did not yet check this in). This change comes down to the following: before, any subelements (including text and/or whitespace) of <data> were accepted as is; now, all text (whitespace or not) as subelement of <data> are ignored. Does this work for you ? Does anybody else have any opinion about this ? Sven -- Sven Van Caekenberghe - mailto:sven@beta9.be Beta Nine - software engineering - http://www.beta9.be .Mac - svc(a)mac.com - http://homepage.mac.com/svc "Lisp isn't a language, it's a building material." - Alan Kay

1 0

[s-xml-rpc-devel] Question about server functions
by Peter Hertmuller 16 Feb '06

16 Feb '06

Hi everybody I'm trying to use the s-xml-rpc stuff to communicate a couple of applications. One of them offers several capabilities required by the others. My question is what I have to do to make available the functionalities of my server? The system has over 100 functions (including macros, variables) and I don't know if what I can do is to extend the s-xml-rpc-exports package with these functions. I don't have so much idea about the packaging system in lisp. I'm using SBCL 0.9.4. Any help is welcome. Thanks in advance for your time Peter

1 0

[s-xml-rpc-devel] S-BASE64 & S-SYSDEPS
by Sven Van Caekenberghe 09 Jan '06

09 Jan '06

From now on, the local sydeps.lisp file is replace by a dependency on the more general S-SYSDEPS package ( http://homepage.mac.com/svc/s- sysdeps/ ) and the local base64.lisp is replaced by a dependency on the equivalent S-BASE64 package ( http://homepage.mac.com/svc/s- base64/ ). Only in CVS HEAD for now, if there are no objections, I will release this soon to the tarballs. Later, I intend to start using both S-HTTP-CLIENT as well as S-HTTP- SERVER to even further simplify the S-XML-RPC code base and to maximize reuse over my open source common lisp packages. Sven

1 0

[s-xml-rpc-devel] Re: Bug in s-xml-rpc::encode-xml-rpc-call
by Sven Van Caekenberghe 23 Dec '05

23 Dec '05

On 21 Dec 2005, at 23:14, Alain.Picard(a)memetrics.com wrote: > Sven Van Caekenberghe writes: >> Alain, >> >> If I understand your fix correctly, you want to interpret NIL >> immediately as an empty array. >> Before, NIL was interpreted as a boolean, no ? >> What would be best ? >> In CL, this very convenient fact (false == empty list) is a problem >> when you want auto typing of arguments. > > Ah, darn, yes, I forgot that it was pulling double duty as a boolean. > > I did this without much tought, because what happened is that a > test I had which used to run stopped running when I went from > xml-rpc to s-xml-rpc, so I quickly discovered interpreting NIL > as a symbol as the culprit. Now I'm not so sure. > > Barring an "official" type mapping between lisp and XMLRPC, > I guess it gets down to you to choose (and to document your choice). > > I think losing NIL as a boolean is too costly a price to pay, > so perhaps forcing user code to use empty arrays instead of empty > lists is an acceptable price to pay. > > So users would have to write code like this > (s-xml-rpc:encode-rpc-call "method" ... (or foo #()) ... ) > > which sucks, but, if they don't like it, they can use vectors > instead of lists as the data type for foo. > > Other marshalling systems, e.g. CORBA, don't have these issues > as they need to declare types up front as part of the method > signature. > > OK, well, thanks for reminding me of the true nature of the problem. > Perhaps the best thing is to simply leave it as is. OK, unless there are others with a different opinion, we will leave it at that for now, the mailing list archive will keep a reference of this issue for future reference. Sven

1 0

[s-xml-rpc-devel] Re: Bug in s-xml-rpc::encode-xml-rpc-call
by Sven Van Caekenberghe 21 Dec '05

21 Dec '05

Alain, If I understand your fix correctly, you want to interpret NIL immediately as an empty array. Before, NIL was interpreted as a boolean, no ? What would be best ? In CL, this very convenient fact (false == empty list) is a problem when you want auto typing of arguments. Any other opinions ? Sven On 21 Dec 2005, at 05:09, Alain.Picard(a)memetrics.com wrote: > Hi Sven! > >> I note that empty arrays and empty lists are not treated >> similarly, to wit: > > This definition of encode-xml-rpc-value > fixes the problem I just reported: > > (defun encode-xml-rpc-value (arg stream) > (write-string "<value>" stream) > (cond ((null arg) > (encode-xml-rpc-array arg stream)) > ((or (stringp arg) (symbolp arg)) > (write-string "<string>" stream) > (print-string-xml (string arg) stream) > (write-string "</string>" stream)) > ((integerp arg) (format stream "<int>~d</int>" arg)) > ((floatp arg) (format stream "<double>~f</double>" arg)) > ((or (null arg) (eq arg t)) > (write-string "<boolean>" stream) > (write-string (if arg 1 0) stream) > (write-string "</boolean>" stream)) > ((and (arrayp arg) > (= (array-rank arg) 1) > (subtypep (array-element-type arg) > '(unsigned-byte 8))) > (write-string "<base64>" stream) > (encode-base64-bytes arg stream) > (write-string "</base64>" stream)) > ((xml-rpc-time-p arg) > (write-string "<dateTime.iso8601>" stream) > (universal-time->iso8601 (xml-rpc-time-universal-time arg) stream) > (write-string "</dateTime.iso8601>" stream)) > ((xml-literal-p arg) > (write-string (xml-literal-content arg) stream)) > ((or (listp arg) (vectorp arg)) (encode-xml-rpc-array arg stream)) > ((xml-rpc-struct-p arg) (encode-xml-rpc-struct arg stream)) > ;; add generic method call > (t (error "cannot encode ~s" arg))) > (write-string "</value>" stream)) > > Cheers, > --ap

1 0

[s-xml-rpc-devel] cmucl port
by Fred Nicolier 04 Nov '05

04 Nov '05

Hi, I wrote some lines to port s-xml-rpc to cmucl. Here is the code from the file sysdeps.lisp : What do you think? >> ;;;; -*- mode: lisp -*- ;;;; ;;;; $Id: sysdeps.lisp,v 1.1.1.1 2004/06/09 09:02:39 scaekenberghe Exp $ ;;;; ;;;; These are the system dependent part of S-XML-RPC. ;;;; Ports to OpenMCL, LispWorks and SBCL are provided. ;;;; Porting to another CL requires implementating these definitions. ;;;; ;;;; Copyright (C) 2002, 2004 Sven Van Caekenberghe, Beta Nine BVBA. ;;;; SBCL port Copyright (C) 2004, Brian Mastenbrook & Rudi Schlatte. ;;;; ;;;; You are granted the rights to distribute and use this software ;;;; as governed by the terms of the Lisp Lesser General Public License ;;;; (http://opensource.franz.com/preamble.html) also known as the LLGPL. (eval-when (compile load eval) #+cmu (require :simple-streams)) (in-package :s-xml-rpc) (defmacro with-open-socket-stream ((var host port) &body body) "Execute body with a bidirectional socket stream opened to host:port" #+openmcl `(ccl:with-open-socket (,var :remote-host ,host :remote-port ,port) ,@body) #+lispworks `(with-open-stream (,var (comm:open-tcp-stream ,host ,port)) ,@body) #+cmu `(let ((,var (make-instance 'stream:socket-simple-stream :direction :io :remote-host ,host :remote-port ,port))) (unwind-protect (progn ,@body) (ext:close-socket ,var))) #+sbcl (let ((socket-object (gensym))) `(let ((,socket-object (make-instance 'sb-bsd-sockets:inet-socket :type :stream :protocol :tcp))) (sb-bsd-sockets:socket-connect ,socket-object (car (sb-bsd-sockets:host-ent-addresses (sb-bsd-sockets:get-host-by-name ,host))) ,port) (let ((,var (sb-bsd-sockets:socket-make-stream ,socket-object :element-type 'character :input t :output t :buffering :none))) (unwind-protect (progn ,@body) (close ,var)))))) (defun run-process (name function &rest arguments) "Create and run a new process with name, executing function on arguments" #+lispworks (apply #'mp:process-run-function name '(:priority 3) function arguments) #+openmcl (apply #'ccl:process-run-function name function arguments) #+sbcl (apply function arguments) #+cmu (apply function arguments)) (defvar *server-processes* nil) (defun start-standard-server (&key port name connection-handler) "Start a server process with name, listening on port, delegating to connection-handler with stream as argument" #+lispworks (comm:start-up-server :function #'(lambda (socket-handle) (let ((client-stream (make-instance 'comm:socket-stream :socket socket-handle :direction :io :element-type 'base-char))) (funcall connection-handler client-stream))) :service port :announce t :error t :wait t :process-name name) #+openmcl (ccl:process-run-function name #'(lambda () (let ((server-socket (ccl:make-socket :connect :passive :local-port port :reuse-address t))) (unwind-protect (loop (let ((client-stream (ccl:accept-connection server-socket))) (funcall connection-handler client-stream))) (close server-socket))))) #+cmu (let* ((socket (ext:create-inet-listener (or port 0))) (handler-fn (lambda (fd) (declare (ignore fd)) (let ((stream (sys:make-fd-stream (ext:accept-tcp-connection socket) :buffering :none :input t :output t :element-type 'base-char))) (funcall connection-handler stream))))) (push (list name socket (sys:add-fd-handler socket :input handler-fn)) *server-processes*)) #+sbcl (let* ((socket (make-instance 'sb-bsd-sockets:inet-socket :type :stream :protocol :tcp)) (handler-fn (lambda (fd) (declare (ignore fd)) (let ((stream (sb-bsd-sockets:socket-make-stream (sb-bsd-sockets:socket-accept socket) :element-type 'character :input t :output t :buffering :none))) (funcall connection-handler stream))))) (setf (sb-bsd-sockets:sockopt-reuse-address socket) t) (sb-bsd-sockets:socket-bind socket #(0 0 0 0) port) (sb-bsd-sockets:socket-listen socket 15) (push (list name socket (sb-sys:add-fd-handler (sb-bsd-sockets:socket-file-descriptor socket) :input handler-fn)) *server-processes*)) name) (defun stop-server (name) "Kill a server process by name (as started by start-standard-server)" #+lispworks (let ((server-process (mp:find-process-from-name name))) (when server-process (mp:process-kill server-process))) #+openmcl (let ((server-process (find name (ccl:all-processes) :key #'ccl:process-name :test #'string-equal))) (when server-process (ccl:process-kill server-process))) #+sbcl (progn (destructuring-bind (name socket handler) (assoc name *server-processes* :test #'string=) (sb-sys:remove-fd-handler handler) (sb-bsd-sockets:socket-close socket)) (setf *server-processes* (delete name *server-processes* :key #'car :test #'string=))) #+cmu (progn (destructuring-bind (name socket handler) (assoc name *server-processes* :test #'string=) (sys:remove-fd-handler handler) (ext::close-socket socket)) (setf *server-processes* (delete name *server-processes* :key #'car :test #'string=))) name) ;;;; eof >> -- Fred Nicolier

2 1

[s-xml-rpc-devel] Port to cmucl + accidental breakage
by Rudi Schlatte 26 Oct '04

26 Oct '04

Hi, I've just checked in cmucl support for s-xml-rpc. In the process, I seem to have deleted allegro support (I wasn't on my development machine, so started from the latest asdf-installable version and didn't diff before committing from my main machine). I'll go restore allegro support now. Rudi

1 0

[s-xml-rpc-devel] Defining remote functions
by Frédéric Brunel 08 Jul '04

08 Jul '04

Hi, By googling the Web for an XML-RPC implementation in Common Lisp, I found S-XML-RPC and other one for Corman Lisp. I'm glad that S-XML-RPC is now part of Common-Lisp.net. By the way, looking at the Corman Lisp API for XML-RPC, I found interesting that it have the ability to define a standard function embedding an XML-RPC call. How about implementing this kind of thing in S-XML-RPC? I wrote the following lines of code: (defmacro define-xmlrpc-method (name args &key url method) `(defun ,name ,args (xml-rpc-call (encode-xml-rpc-call ,method ,@args) :url ,(puri:uri-path url) :host ,(puri:uri-host url) :port ,(cond ((puri:uri-port url)) (t 80))))) (define-xmlrpc-method get-state-name (state) :url #u"http://betty.userland.com/RPC2" :method "examples.getStateName") (define-xmlrpc-method get-time () :url #u"http://time.xmlrpc.com/RPC2" :method "currentTime.getCurrentTime") ? (get-state-name 41) "South Dakota" ? (get-time) #<XML-RPC-TIME 20040617T10:47:31> I rely on the great PURI package to parse URL. Quite straightforward. Of course, we should also wrap and unwrap some type convertions not to see anything about the XML-RPC types. I guess the function should also accept HASHTABLEs to be converted in XML-RPC structs. What do you think? -- Frederic Brunel

2 3

[s-xml-rpc-devel] New extensions
by Rudi Schlatte 18 Jun '04

18 Jun '04

Hi, I just checked in support for system.getCapabilities and added standard error codes (I hope I didn't miss any places). The stuff beyond the basic protocol now lives in extensions.lisp, and there are some tests (not comprehensive at all, but it's a start). Lastly, it's now possible to send symbols over the wire; they are encoded as strings. I've now officially run out of things to implement in the code; perhaps I'll write a manual next (depending on the weather and enthusiasm on the weekend, and on Sven's willingness to accept texinfo). Cheers, Rudi

2 1

[s-xml-rpc-devel] system.multicall implemented
by Rudi Schlatte 13 Jun '04

13 Jun '04

Hi, So system.multicall is implemented in CVS as well. See http://www.xmlrpc.com/discuss/msgReader$1208 for the spec. I multi-called some methods from Python and it looked ok (both normal return values and faults "looked the same" as the examples in the spec). I introduced a literal string so the fault structures can be stuffed in the result array without being turned into strings with xml in them. Now all of the xml-rpc extensions I know of are implemented; if there's another one I'll likely move the lot into their own file so they don't clutter up the main server code. Cheers, Rudi

1 0