Hello Drake,

There is some confusion around the whole SOAP/REST issue, so let me try and calrify things:

Initially, we only supported SOAP.

Then, due to many users requests, we added the asp-dotnet-out-of-the-box zero-effort HTTP-POST/GET support.

This is done simply enabling a flag in our opencalais asp.net webapp, and is completely implemented by .NET frmaework  .

The URL for this was http://api.opencalais.com/enlighten/calais.asmx/Enlighten   .

This was a temporary solution, until we add our own REST support, and this solution got the name "HTTP-POST", and I'm still not sure how/why:  It also allows HTTP-GET ...

The downsides of this were:

1.  The response was wrapped in a <string> element, and you had to unescape the contents, to get the response in XML format.

2. It contained the explicit "calais.asmx" page-name, which we never intended to.

So, then came our REST solution, which again is both HTTP-GET and HTTP-POST.

In order not to get it all mixed-up with the earlier, we call it REST everywhere.

The URL for this is http://api.opencalais.com/enlighten/rest/      .

(including the trailing slash)

This URL is both for POST and GET, and is the recommended one.

It returns the response directly, without and "envelope", and is more straight-forward.

So, you are welcome to use it   -   it is there to stay!

Now, about your text-length issue:

There is a limit on URL length in various places, some of them are client-side (browsers), some of them are server-side.

Insisting on sending 100K through the URL is really just hitting the wall, when you have a perfectly good and easy workaround: HTTP-POST  .

So, please use our latest REST URL  .  Combined with HTTP-POST, you should be good-to-go ...

HTH

Meir