RE: [twsocket] Latest revision May, '05 entering URLs

2005-05-27 Thread Maurizio Lotauro
On 26-May-05 18:00:21 Bob Herbst wrote: >Maurizio, >I am supposed to receive a time statement that the one line reads something >like this: >'53516 05-05-26 05:53:52 50 0 0 754.9 UTC(NIST)' >This is a coded time statement that I parse and use to reset my computer's >time. That is all that is t

RE: [twsocket] Latest revision May, '05 entering URLs

2005-05-26 Thread Darin McGee
Bob, How right you are, I will have to give the demo a try myself. Darin From: [EMAIL PROTECTED] on behalf of Bob Herbst Sent: Thu 5/26/2005 2:24 PM To: ICS support mailing Subject: RE: [twsocket] Latest revision May, '05 entering URLs Darin, I

RE: [twsocket] Latest revision May, '05 entering URLs

2005-05-26 Thread Bob Herbst
latest ICS revisions, so for now, it is history for me. Bob -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Francois PIETTE Sent: Thursday, May 26, 2005 2:41 PM To: ICS support mailing Subject: Re: [twsocket] Latest revision May, '05 entering URLs The url

Re: [twsocket] Latest revision May, '05 entering URLs

2005-05-26 Thread Francois PIETTE
> I just tested with my IE the http://132.163.4.102:13 and the > http://132.163.4.102:14 and both respond with a time line. > > But neither of these work with the ICS demo's. > > Still asking 'what am I missing with the ICS?' ICS HTTP component expect to receive a valid HTTP response. IE silentl

Re: [twsocket] Latest revision May, '05 entering URLs

2005-05-26 Thread Francois PIETTE
> I have also tried the '132.163.4.102:13' fails and shows 501 Protocol > not implemented I've found and fixed this bug. Thanks. You'll see the code in the next refresh. > http://132.163.4.102:13 and they both do not work. 0 bytes received. :( Port 13 !? -- [EMAIL PROTECTED] http://www.o

Re: [twsocket] Latest revision May, '05 entering URLs

2005-05-26 Thread Francois PIETTE
riginal Message - From: "Bob Herbst" <[EMAIL PROTECTED]> To: "ICS support mailing" Sent: Thursday, May 26, 2005 7:00 PM Subject: RE: [twsocket] Latest revision May, '05 entering URLs > Maurizio, > > I am supposed to receive a time statement that the one l

RE: [twsocket] Latest revision May, '05 entering URLs

2005-05-26 Thread Bob Herbst
[mailto:[EMAIL PROTECTED] Behalf Of Darin McGee Sent: Thursday, May 26, 2005 12:14 PM To: ICS support mailing Subject: RE: [twsocket] Latest revision May, '05 entering URLs Bob, port 13 is the Daytime protocol - the samples do not support receiving the daytime protocol. That is left for you

RE: [twsocket] Latest revision May, '05 entering URLs

2005-05-26 Thread Bob Herbst
this site. Bob -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Maurizio Lotauro Sent: Thursday, May 26, 2005 12:11 PM To: ICS support mailing Subject: Re: [twsocket] Latest revision May, '05 entering URLs Scrive Bob Herbst <[EMAIL PROTECTED]>: > Hello

RE: [twsocket] Latest revision May, '05 entering URLs

2005-05-26 Thread Bob Herbst
] Behalf Of Bjørnar Nielsen Sent: Thursday, May 26, 2005 11:10 AM To: 'ICS support mailing' Subject: RE: [twsocket] Latest revision May, '05 entering URLs > I have also tried the '132.163.4.102:13' fails and shows > 501 Protocol '''' > not imple

RE: [twsocket] Latest revision May, '05 entering URLs

2005-05-26 Thread Darin McGee
Bob, port 13 is the Daytime protocol - the samples do not support receiving the daytime protocol. That is left for you to implement. Darin From: [EMAIL PROTECTED] on behalf of Bob Herbst Sent: Thu 5/26/2005 10:06 AM To: Twsocket@Elists.Org Subject: [twsocket]

Re: [twsocket] Latest revision May, '05 entering URLs

2005-05-26 Thread Maurizio Lotauro
Scrive Bob Herbst <[EMAIL PROTECTED]>: > Hello Francois, > > I am doing some updating of my programs and I ask is there something that I > am doing wrong? I tried http://132.163.4.102:13 and what I see in the browser is in the header. This is why it seems that you don't receive anything. Bye,

RE: [twsocket] Latest revision May, '05 entering URLs

2005-05-26 Thread Bjørnar Nielsen
> I have also tried the '132.163.4.102:13' fails and shows > 501 Protocol > not implemented I had some similar error. When I inserted http:// in fron of the url, the error disapeared. Regards Bjørnar -- To unsubscribe or change your settings for TWSocket mailing list please goto http:/