Re: TiniHttpServer and GPRS or Tynamo?

Shawn Silverman <[email protected]>
Newsgroups gmane.comp.hardware.microcontrollers.tini
Message-ID <[email protected]>
Sockets on the TINI have been known to stay open when they are supposed 
to be closed.  I've seen this behaviour in all of the TINI releases, 
including the latest.  Perhaps this is what you're seeing.  Although, I 
usually see things stuck at a "CLOSED_WAIT" state.

Are you saying that TINIWebserver works, but none of the servlet 
servers do?  If that is the case, what exactly is working?  An HTML 
page?  Have you tried serving just HTML from, say, Tynamo, and is the 
behaviour the same?

	-Shawn

On 2-Apr-04, at 4:46 AM, Simon wrote:

> No, the modem doesn't do anything different when connected to GPRS, as 
> far
> as the TINI is concerned, it has a normal PPP connection via serial to 
> the
> internet.
>
> I am wondering whether there is some difference between the basic
> TINIWebserver, (which works under GPRS) and the more advanced servlet 
> web
> servers (TiniHttpServer, Tynamo and IWS)  As I mentioned before, I have
> static IP GRPS, but for security reasons I have very few open ports on 
> that
> IP address. (Currently only port 80)
>
> Now, my question is, do servlets require another connection to be 
> opened on
> the TINI apart from the standard listening port, (in my case port 80?)
>
> This would explain why the remote browser connects to the TINI, and 
> netstat
> reports a FIN_WAIT state on port 80, before the web browser times-out 
> its
> request.
>
> Anyone have any ideas?
>
> Simon

_______________________________________________
TINI mailing list
TINI-6tN4nzCoH/[email protected]
To UNSUBSCRIBE, edit your profile, or see list archives:
http://lists.dalsemi.com/mailman/listinfo/tini
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.