Re: disappointed with URL Access Scripting
Re: disappointed with URL Access Scripting
- Subject: Re: disappointed with URL Access Scripting
- From: "John R. Head" <email@hidden>
- Date: Tue, 07 May 2002 15:35:16 -0500
I did not have your original post to review, but I have delivered some
solutions on URL access and it does have its limits.
I have found it you create a 3background2 page that has only the response to
a post on it, but bracketed with something you can wrap like 2|2 vertical
bar, you can use AppleScript delimiters to find the response.
Also if you run an encode and decode routine on the information before the
post, it does seem to help as you are sending HTTP correct information via
this method. We were accessing a direct action in WebObjects that understood
the order of data we were sending, but we did have to run an encode on it to
fix some problems with some data being mangled without an encode process. I
have found some routines that do a great job of encoding user friendly text
into internet friendly text.
ALSO not documented very well is the fact that URL ACCESS could NOT post
over 256 total characters in the past, do not know if this has been fixed.
We ended up writing files directly to the server and them read after started
by a post 3your file is there, read it2 and we were able to work around
that problem.
John R. Head, CTO
Visionary Media Inc
www.visionary-media.com
512-258-7311
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.