Re: IP Push I Guess ??

Thanks to all.

TCP/IP was the layer at which a lot of info about how the whole thing fits
together was found. One interesting thing I found which I wasn't aware of
was the way buffering of packets occurs. I mean, once you know the pulses
that are the bits and bytes that are the characters that is the html file
you are sending is broken up into packets, you could take a punt that each
packet is numbered and has the total number of packets in the parcel
identified [e.g 3 of 7] so the receiving end simply puts the packets
together in sequence once it's got them all.

What I didn't realise is that the receiving end sends to the sending end
just how much memory it has made available for packets and it changes this
number when it see's what packets it's got already. If you send more than
that ammount of memory it currently has made available it wont take the
packets.

That is, there's a bit more two way stuff going on that I initially thought.

[Correct if I'm wrong ...]

My end point was served by simply having the remote script:

1.  Return a "done - thankyou" page over the connection created on the form
submit
2. Creating a new connection sending a "form" of data to a script on my
local server.
[I have access to the remote script]

HWG hwg-techniques mailing list archives, maintained by Webmasters @ IWA