Well a component would seem the best way to go here, if you are really
intent on using Telnet. Sounds like you need to find a host that will allow
them.
But perhaps a better option would be to take a step back and think about
what you are trying to acheive and why you would want to do this? You might
be able to get the data you want from this telnet system via a different
route or via some form of extract that you can then use for your ASP site in
a much more efficient way. An ASP page that is connected to a telnet
session might not be very responsive going forward - especially if you want
to keep that session open across multiple page requests for one user.
Assuming that you need to keep the telnet session open, how are you going to
handle interactions with the telnet session across the ASP session? You
wouldn't want to store this telnet component in a session variable for
instance and then have multiple users each using the component stored in a
session variable - your site will grind to a halt pretty quickly. You can't
store it at application level either. Are multiple users going to be using
your site at the same time?
Richard
