AutoSMS API - session state required?

[David]

As a follow up to http://groups.google.com/group/anonytext/t/76011ccab21f0f71

API works great but this is the only question/issue I've come across,
that's not documented for the API. Guess not many people deploy the
API in various environments.

I worked on implementing API based clients across multiple platforms,
mostly browser extensions (Opera, Chrome, Safari) and desktop/web
gadgets, etc.

In my work, I've noticed that with the API, can't send message for
certain platform implementations. Everything works up until you send
the message, where API returns: "Error: Please enter the code as
shown". I know it's not a problem with typing wrong code or wrong
number/carrier because they work in other platform implementations. So
my best guess is some missing session state support on the platform.
Or some hidden HTTP header info that isn't processed correctly by some
platforms. So was wondering if the API actually uses session state
checking in addition to the CAPTCHA code verification that isn't quite
documented.

FYI, the only platform implementations I run into this problem so far
are: iGoogle gadgets (which uses iFrames or something like that), and
desktop based Microsoft HTA applications on Windows where browser is
Internet Explorer 5.x or 6.x. The HTA app works fine when browser is
IE 7+. Probably has to do with the XmlHttpRequest support in versions
of IE.

If session state is required, then implementing API clients using
languages/platforms like .NET or Java, etc. may require enabling
(session state) cookie support. Something worth documenting for API.

If it is session state requirement or if we can track down cause of
problem, it would be nice to enhance error message returned to help
API developers debug. Because the current message does not correspond
to actual problem, and is misleading.

[Karl Morris]

Hi David,

While much wasn't written on it, the documentation does mention that
all client applications must maintain session state (session
awareness). That blurb is in the _Get the authentication code_ step
under the "Sending a message using API calls" topic.

As you stated, it works with IE7+, and of course it works under
Firefox, so I would tend to agree that it might have something to do
with different versions of IE. In fact, I'd bet my hat on it. Have you
had any issues at all with Chrome or any other platform (ie, a less
than straightforward implementation, even if you got it working
eventually)?

On Feb 13, 4:05 pm, David <manga...@gmail.com> wrote:
> As a follow up tohttp://groups.google.com/group/anonytext/t/76011ccab21f0f71

[David]

Thanks Karl, must have overlooked that section in the API doc.

No real issues on Chrome or other browsers. It was actually pretty
easy to port to each browser, after you figure out their formats.

FYI, the Chrome version is officially available here (though not as
pretty as your Firefox version):

https://chrome.google.com/extensions/detail/ldchbhmddhdbdbhlmhhbbmimlaakplol

Sadly, I couldn't get the other browser extensions accepted for
official distribution by their browser vendors yet. So I host the
other ones on my own page.