To get a pretty good idea of the time to that server you can do a trace route (tracert servername) and not the IP of the last response. That's usually a firewall or router near the target server, so it gives pretty good approximate ping times. In my experience usually 1-5 ms lower than the target.
HTH, Roger C. Morgan II [EMAIL PROTECTED] --- In [email protected], Dave Sellers <[EMAIL PROTECTED]> wrote: > > Hi Roger. > > That's a good point. > > I'm of the opinion that 150mS is pretty good - the SMTP server machine > does not respond to pings but pinging www.google.com ought to be fairly > quick and takes 40-50ms on my broadband connection. I'll get my > customer to try it from his server.. > > Regards > Dave > > Roger C. Morgan II wrote: > > >Just a question to think about, what is the latency (ping time) from > >the source to the destination? > > > >I just looked at the RFC, to send a message on an already > >established connection it looks like there are 4 > >command/acknowledgement pairs. Depending on the latency that alone > >can eat up a fair portion of your 150ms time. If the destination has > >any delay responding, that would also eat up that time. > > > >If the source and destination are a couple of thousand miles apart > >150ms may be about the best you can get. If they are in the same > >building, you may be able to get much better. > > > >HTH, > > > >Roger C. Morgan II > >[EMAIL PROTECTED] > > > >--- In [email protected], Dave Sellers <[EMAIL PROTECTED]> wrote: > > > > > >>Hi All > >> > >>I have written a small app which, having identified a certain > >> > >> > >condition > > > > > >>needs to get an email into a particular mailbox as quickly as > >> > >> > >possible. > > > > > >>The email is simple plain text of only about 550 characters. > >> > >>The app is running on a dedicated, hosted server so I'm content > >> > >> > >that its > > > > > >>internet connection is as fast as economically possible. I'm > >> > >> > >doing a > > > > > >>DNS resolution to get the IP address of the preferred SMTP server > >> > >> > >at the > > > > > >>destination domain. I use the Indy TIdSMTP component (Indy 9) and > >> > >> > >I > > > > > >>have code in place which ensures that it remains connected to that > >> > >> > >SMTP > > > > > >>server ready for when I need it. It's taking about 150ms on > >> > >> > >average for > > > > > >>the call to Send() to return. > >> > >>I realise that the Indy newsgroups are the place for guidance on > >> > >> > >best > > > > > >>use of their components but what I'm wondering is if anyone can > >>recommend a faster alternative method of delivering an email? > >> > >> > >Maybe > > > > > >>150mS is as fast as I can hope for? I guess I could just use a > >> > >> > >socket > > > > > >>and do what the Indy component does but I doubt (I know!) I > >> > >> > >couldn't do > > > > > >>a better job than the Indy team. Am I missing a trick here, is > >> > >> > >there an > > > > > >>alternative method or an alternative component that will get the > >> > >> > >job > > > > > >>email delivered quicker? > >> > >>TIA > >>Dave. > >> > >> > >> > > > > > > > > > > > > > > > >----------------------------------------------------- > >Home page: http://groups.yahoo.com/group/delphi-en/ > >To unsubscribe: [EMAIL PROTECTED] > >Yahoo! Groups Links > > > > > > > > > > > > > > > > > > > > > ----------------------------------------------------- Home page: http://groups.yahoo.com/group/delphi-en/ To unsubscribe: [EMAIL PROTECTED] Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/delphi-en/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
