Hi all,

maybe someone has one or more answers and let's me know:

(environment is Squeak 2.6 on NT4.0/SP4)

1) PWS>>reply:
 When replying using PWS (PWS>>reply:) I found that on a local host one does
not need to send

PWS success.
PWS contentHTML; crlf.

But when I tested the stuff over the Internet it didn't work. I had to add
the two lines mentioned before. Why?

2) PWS/Sockets
When testing on a local host I found that clicking too fast in a browser
Squeak would not respond anymore. Any clues?

3) Low on memory
When Squeak runs low on memory it puts up a dialog. I accidentely clicked
besides the dialog and the dialog vanished behind the browser. I could not
find a way to get the dialog back. I had to quit the image. Any solutions?

4) ServerActions vs. WebPages
Conceptually I have trouble understanding the need/use of ServerActions with
regard to a web page. After all, a web server responds with pages and not
actions. For example: ChatPage is a subclass of ServerAction, but to say
that a ChatPage is-a ServerAction... Has someone pointers to standard
solutions/concepts for designing a web server with many different pages
(i.e. where each page is formed differently and behaves differently at the
client side). Smalltalk embedded in HTML is not suitable for my purposes, I
think (maintaining a customer and order database and several reports).
Anyone?

Thanks in advance,

Reinier.