Re: [Dynapi-Help] Simple communication questions...

[Cristian G. <cri...@pr...>]

> documents on the server.  But most computers are compiled with 65535 sockets
> by default I believe.  I am not sure if any operating systems allow for this
> number to be increased.  I suspect that OSes like Linux and FreeBSD would
> allow this to be increased, by hacking the source code.  It may or may not

A network socket is a structure composed by an IP address, a port number 
and an IP protocol (TCP or UDP). There can only be 65536 ports on one 
IP; however a machine can have multiple IP addresses. Anyway, that's not 
the point :)

>>The Push/Pull technique should work with all supported
>>web browsers.

... provided the user has the Java Runtime Environment (JRE aka JVM - 
Java Virtual Machine, the bytecode interpreter) installed and enabled in 
browser. As you know, Microsoft no longer ships a JVM with Windows, it 
has to be downloaded from Sun website and installed. The user might not 
be able to do it (not having administrative rights, company software 
policy, bandwidth limitations).

A Java applet opening a TCP connection back to the server will fail if 
the user is behind a firewall (only allowing connections to certain 
ports, 80 and 443 for example) or behind a (socks) proxy. The HTTP 
protocol, as Leif said, is stateless (well, sort of, if not using 
keep-alives) meaning the browser makes a request, the server responds 
then the connection is closed.

>>The API will handle all the technical
>>details so the user only have to listen in for an
>>event from the server.
>>What do you think?

Why not using asynchronous techniques, for instance polling a dynamic 
server page (PHP/ASP/JSP/CGI), writing the result in an iFrame or hidden 
frame?

I would stay away from Java as much as possible.

>>Raymond Irving
 > Leif

Grig