Take a look at
http://www.santronics.com
It gives you exactly what you need for dialup and telnet operations, (and
web and ftp and Windows GUI). The interface is virtualized and 100%
programmable so whether you dial in or connect via telnet, the same logic is
used of offering XYZK (Xmodem, Ymodem, Zmodem, Kermit) file transfer
protocol. Uploads/Downloads are centralized by the server so it is
presentable via Text (Dialup/Telnet), WEB, FTP or GUI.
The basic framework is client/server where client hosting servers use
wcBASIC which is a common language runtime (CLR) p-code language written
specifically for client/server operations. So when a dial up or telnet
connection arrives, it called the top level MAIN.WCX application, which
links in other WCX to provide the text menu interface. Basic installations
come with default library of wcBASIC code to provide the classic Text and
Web interface. The source code is available for purchase with many of
customer customized. All client software is written using the SDK available
for C/C++, Delphi, VB, Java, Visual FoxPro and soon .NET. I recently
created a simple .NET Wildcat! client using I guess what they call unmanaged
code.
You can write you own client software that uses the 100+ SDK server
functions. Every action comes with a reaction in this system so there a
suite of server events you can watch for, such as File Uploads, Downloads,
even Instant Messaging!!
It also checks for special WCX hooks for some of these events, if any, for
example, SCANFILE.WCX is called when a file is uploaded via Dialup or
telnet.
Many of our clients use these hooks to interface the system with there
backend system (Medical, Payroll, Insurance companies, etc, #1 system in the
market used by the biggest of the biggest)
So when a file is uploaded, you can do something like copy it to another
drive or something to do some "file processing." Same with the WEB
(httpScanFile.wcx), FTP (FtpScanFile.wcx), etc. Or, you can write SDK
application and have the system signal you with a callback function to tell
you that a file has been uploaded! Endless capabilities!
So you don't have to re-invent the wheel and spend YEARS engineering a
solid, reliable and secured frontend hosting client/server system. It is
all available in this package, yet, you have the flexibility to customize
and program your application.
--
Hector Santos
WINSERVER "Wildcat! Interactive Net Server"
support:
http://www.winserver.com
sales:
http://www.santronics.com
"Neel Word" <an*******@discussions.microsoft.com> wrote in message
news:52****************************@phx.gbl...
I need to develop an application (development platform:
Win2000; target platform: Win98/ME/NT4/2000/XP), which
would require file transfer functionality over dial-up and
network.
We could develop on .NET (1.1 or 1.0 - VS.NET 02/03) or
using plain COM (visual c++). We'd prefer .NET though.
Does anyone know of any products or COM API (or .NET
classes) that can easily handle file transfer over dial-up
(given a phonenumber), or network (given ip-address or
computer name)?
The sending and receving would both be running the
application that we are developing.
I looked at NetMeeting 3.0 API but it appears that it does
not support dial-up (PSTN)...
Any help or ideas will be greatly appreciated.
Thanks
