Quote:


As you know, Sesame does not embed images in the application file itself. Rather, it stores the path or URL to the image. So, to save the actual image from within Sesame, you would need to use the SBasic HTTP commands and decode the image. Why do you want to do this from within Sesame instead of allowing Sesame to retrieve the dynamic image from Google or pre-retrieving image and using that in Sesame?

I'll look into it.

Edit: I did look into it. On Linux the connection times out harmlessly. On Windows the program will wait until the OS times out the connection - a period of time longer than I was willing to wait. In neither case did Sesame crash. I could probably force a time out on the connection itself (rather than counting on the OS for a reasonable value), though I'm not sure how long is long enough, yet not too long.

Thanks Mark and Hammer.
It was a great help to explanations and suggestions.

It is very atypical that a security proxy would require a password for each connection. That would make viewing a modern web page like cnn.com require dozens of password requests as it loads because that page is comprised of "pass-through" connections to multiple servers all on a single page - many simply to serve the advertising that appears on the page. So I am guessing that your proxy is requiring a password for each new top level connection. If that is the case, you will probably have to either log in to the same connection by hand (in a browser) once before invoking Sesame through the same proxy connection, or you will have to reconfigure the terms of the proxy. I recommend that latter solution. Speak to your administrator about what you are attempting to do and see if they can help you configure a more reasonable connection.

The only reason to configure a proxy with an ongoing stream of passwords is to discourage internet connections in general. If this connection is being used to add value to your company, it is very likely an "exception" could be made for google maps or charts.