RE: Maintaining XML via Form Post

Hey Karl,

Our product posts xml from our web clients--a browser.

Here are a couple of  reasons why this is good:
   1.  We have been able quite easily migrate these to web service calls.
   2.  You have a logically encapsulated, well-formed request that saves
server-side overhead in having to build a complex request structure out of a
query string or form fields, as well as providing an standard API (schema)
to your server-side request consumers.

But, your question:
>>There are many form posts (many trips back to
>>the server).  Is this a good idea?

I don't quite understand.  Why are there many posts?  What does that have to
do with submitting a post with an xml body?
Are building xml via the posts?  If so, then I definitely think that is a
bad idea ... unless you don't have any scalability demands.  And why not
build the xml on the client?  If you need to get server-side input to drive
its content, then I'd suggest batching your calls as much as possible.

Also, I think you may want to post your question on some other lists,
because this isn't really an xsl related question ... it sounds more like an
application design question.

Jeff


-----Original Message-----
From: Karl Stubsjoen [mailto:karl@xxxxxxxxxxxxx]
Sent: Thursday, February 20, 2003 10:11 AM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject:  Maintaining XML via Form Post


Hello,

I'm considering maintaining an XML object (string) in a form post... What
are the potential pitfals?
I'm writing a little maintenance screen which collects information and
stores it in an XML document.  There are many form posts (many trips back to
the server).  Is this a good idea?  If not, is there a better way to
maintain this XML document?

Karl


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list