tim@grenada.uucp (Tim J Ihde) (03/19/91)
I am starting some major development work that will entail several client/server relationships. I have been told that sockets are falling out of favor in this area. Given that we will be initially working on Sun SPARCStations, and hopefully moving to System Vr4 before too long, the question becomes: what should we use in place of sockets? I have one group of people telling me that TLI is the only way to go, but RPC seems a cleaner interface to me. Is RPC a sun-ism that will soon pass away? Is TLI more "blessed" by standards organisations (ISO, X/Open, etc)? Any input is appreciated. Thanks! tim -- Tim J Ihde tim@grenada.bellcore.com (908) 699-2487
brnstnd@kramden.acf.nyu.edu (Dan Bernstein) (03/19/91)
In article <1991Mar19.004054.8840@bellcore.bellcore.com> tim@grenada.bellcore.com writes: > I have been told that sockets are falling out of favor in this area. Sockets have been the de facto standard for years, and despite rumors begun by certain vendors, sockets will remain the de facto standard for the foreseeable future. Use them. This has been thoroughly discussed before. If you want you can pick up an archive of the latest comp.protocols.tcp-ip argument on the subject via anonymous ftp to 128.122.128.22, pub/hier/inet/socketstream{,.MW,.Z}. > Is > RPC a sun-ism that will soon pass away? Many vendors provide many different remote procedure call mechanisms. If you applications are sufficiently constrained that they work under some RPC then you might as well use it, but you shouldn't expect RPC to be as portable or as widely applicable as sockets. > Is TLI more "blessed" by > standards organisations (ISO, X/Open, etc)? No. ---Dan