Hi all,
I was wondering what the community felt was the best HTTP client we have to date in Squeak (3.8)? I know the term "best" is quite subjective, but what I need to do is automate some web server testing so I need an HTTP client that can GET and POST, has a simple interface, and maybe exposes the result sets from the server in some structured way. I want to "test" some XHTML streams coming out of my seaside web server..
Currently I am getting experienced with the class HTTPSocket in Network-Protocols. There is also an HTTPClient package on SM. Which should I use or should I explore any other options?
Regards,
John
John Pierce wrote:
Hi all,
I was wondering what the community felt was the best HTTP client we have to date in Squeak (3.8)? I know the term "best" is quite subjective, but what I need to do is automate some web server testing so I need an HTTP client that can GET and POST, has a simple interface, and maybe exposes the result sets from the server in some structured way. I want to "test" some XHTML streams coming out of my seaside web server..
Currently I am getting experienced with the class HTTPSocket in Network-Protocols. There is also an HTTPClient package on SM. Which should I use or should I explore any other options?
Hi John,
I can't give you much insight into the two clients; I've found that HTTPSocket is fine if you just want to do simple fetches from HTTP urls. HTTPClient may provide more capability or control, but I don't know that.
Something else you might find interesting, however, is HttpSmallUnit. It's a Camp Smalltalk project that does SUnit-style testing of web-based apps over HTTP. It's currently implemented for VW, and there were plans for a Squeak port, but I don't know if anything has come of that. You may find it's less work to port that than roll your own.
(And, since I haven't provided a useful answer to your question, I'm waiting expectantly for your second post here, saying "Ok, I'm porting SmallHttpUnit to Squeak.... what's the best http client to use?" ;-)
Colin
John,
HTTPClient is what you would want to use if you'll be dealing with raw x/html, usually it's used for web browsers and clients - scamper, monticello and the like.
You may wish to join the seaside mailinglist and search around there, I remember a lot of posts concerning seaside testing. You can do it externally (like Blaine and Roger's SmallHttpUnit), or you can do it internally with SeasideTesting to test the state of the objects.
Colin
On Tue, 14 Dec 2004 17:52:47 -0500, John Pierce john.raymond.pierce@gmail.com wrote:
Hi all,
I was wondering what the community felt was the best HTTP client we have to date in Squeak (3.8)? I know the term "best" is quite subjective, but what I need to do is automate some web server testing so I need an HTTP client that can GET and POST, has a simple interface, and maybe exposes the result sets from the server in some structured way. I want to "test" some XHTML streams coming out of my seaside web server..
Currently I am getting experienced with the class HTTPSocket in Network-Protocols. There is also an HTTPClient package on SM. Which should I use or should I explore any other options?
Regards,
John
It is not because things are difficult that we do not dare, it is because we do not dare that they are difficult. -- Seneca
squeak-dev@lists.squeakfoundation.org