Hi Geof,
Thanks for your answers. See my comments in the text.
Geoff Crawford wrote:
At 05:36 PM 5/20/2007, Jean-Baptiste BRIAUD wrote:
Yes, I'm developping the server, so I everything is open.
I'd totally switch things then.
I used SOAP on a previous project and it is dam' slow.
SOAP is actually not slow at all, the biggest issue is
the transfer of the WSDL. That is assuming you're working
with a parser building the request via the WSDL. If you
figure you already know the API at the other end, you can
just build the SOAP request without the WSDL. And that's
plenty fast and has maybe a few extra bytes compared to
plain XML.
SOAP is slow, not just for wsdl transfer, I found it verbose and really
slower than XML-RPC just one layer above.
In fact, it was measured, not just felt. We compare it to XML-RPC that
won the match, from far.
The only arguments could be the implementation we used for the protocol,
witch I forgot since it was 2 to 3 yers ago now.
XML-RPC could be OK but I would prefer having my own XML.
Why? It seems like there's probably a lot more you'r not
saying. XML is actually far more overhead than SOAP.
SOAP uses the XML but the leap from pure data -> XML
is far slower than XML -> SOAP.
Because of type and verbosity. Type is too poor in XML-RPC, no date type
... I really prefer my own simple XML that reflect a form with a dataset.
I do not have any constraint to be called from elsewhere and even, it
could be done later on like another server facade.
I fully agree : nothing by the URL.
Could you confirm that the following code snipset ensure that data
won't be transmitted via URL :
LzParam.addValue("xml", theXmlText, false)
// I assumed the last parameter set to false ensure that.
I don't believe it does anything of the sort. As far as I know
(and I do admit I'm not an experienced Laszlo expert), lzParam
is just building values. What you do with the values is
entirely separate. So what do you do with that lzParam variable?
I use ds.setQueryString(param);
where ds is a LzDataSet and param a LzParam.
LzParam doc on that last parameter is
enc Boolean If true, URI-encodes the value
That's what matters, not building the parameter list.
Somehow that's got to translate into the request being labeled
as "POST" instead of "GET". Then the parameters have to be
sent in the body of the request, *not* the URL.
How to you do that in lzx ?
So, how do I build my XML on laszlo side ?
You create an XML object, then use the DOM to build data
nodes, set their values, set attributes of nodes, etc..
I'm not sure how to do that in lzx as I'm still learning javascript.
I suspect performance issue with the DOM stack ...
Is it just string concatenation ?
NO.
Is there more efficient than that ?
Do I just pass that XML as a request paremeter ?
Or is there other way than parameter to pass a large text to an HTTP
request ?
You post the whole thing as the body, that's it.
I agree with you, but how do you do that in lzx ?
=====================================================================
Geoff Crawford Phone: (973) 361 - 4224
Innov8 Computer Solutions, LLC FAX: (973) 537 - 6946
711 Route 10 East, Suite 204 Email: [EMAIL PROTECTED]
Randolph NJ 07869 Web: http://www.innov8cs.com
Progress Blog: http://blogs.ittoolbox.com/database/progress/
Take a Step Up to StepUp Accounting
