Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-pascal / 2000-11

ssockets

7 messages · 5 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Mirek a Marcela

Hello,

I've not found st similar to ssockets.pp for Win32. Does it exist?

Mirek Novak

md
to Mirek a Marcela

You will need to interface directly to Win32 - May I suggest looking at Winsock 2.

The attached file is some of the WIN32 interface to Winsock 2. The standard winsock.pas stuff will handle the rest.

Mark
Atlanta, GA

Mirek a Marcela wrote 10 lines
Hello, I've not found st similar to ssockets.pp for Win32. Does it exist? Mirek Novak _______________________________________________ fpc-pascal maillist - http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Unknown author
to md
md wrote
You will need to interface directly to Win32

This is not true; ssockets() should function on win32 as well, it hasn't been tested, however.

- May I suggest looking at Winsock 2.

Using winsock 2 would make your application dependent on win32, and not unless you know the application is only supposed to run on win32, I would not do that.

Michael.

Mirek Novak
to Unknown author

píše:

Show quoted text 7 lines
On Sat, 4 Nov 2000, md wrote: > You will need to interface directly to Win32 This is not true; ssockets() should function on win32 as well, it hasn't been tested, however.

I've tried to compile it under win32 and it had failed. In the source code I've found some possibly unportable /by my opinion/ things like unix sockets.

Unit sockets is ported and works fine but ssockes is interfaced only to Linux.

Mirek Novak

Michael Van Canneyt
to Mirek Novak
Mirek Novak wrote 18 lines
p��e: > On Sat, 4 Nov 2000, md wrote: > > > You will need to interface directly to Win32 > > This is not true; ssockets() should function on win32 as well, it hasn't > been tested, however. > I've tried to compile it under win32 and it had failed. In the source code I've found some possibly unportable /by my opinion/ things like unix sockets. Unit sockets is ported and works fine but ssockes is interfaced only to Linux.

I will try to fix this in the coming days. Unix-sockets are also possible under Windows; I shall try to implement them.

Michael.

md
to Unknown author: This is not true; ssockets() should function on win32 as well, it hasn't been tested,…

I would take Michael Van Canneyt's advice seriously in principle.

But in reality, the only input I can give is that Windows NT4.0 socket performance sucks. And is unstable. Winsock 2 at least gives you some increase over standard sockets.

I say unstable because Microsoft probably knows some trick on getting it to work well, but they have not documented it.

So I say that you create your own interface that wraps the specifics of Win32 as much as possible. That way portability
is somewhat achieved.

Portable code is important, Win32 requires much tweaking and trial and much error before
it works. May I suggest Linux as a more capable platform?

Mark Diener

Show quoted text 19 lines
On Sat, 4 Nov 2000, md wrote: > You will need to interface directly to Win32 This is not true; ssockets() should function on win32 as well, it hasn't been tested, however. > - May I suggest looking at Winsock 2. Using winsock 2 would make your application dependent on win32, and not unless you know the application is only supposed to run on win32, I would not do that. Michael. _______________________________________________ fpc-pascal maillist - http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Mirek Novak
to md

md píše:

Show quoted text 16 lines
I would take Michael Van Canneyt's advice seriously in principle. But in reality, the only input I can give is that Windows NT4.0 socket performance sucks. And is unstable. Winsock 2 at least gives you some increase over standard sockets. I say unstable because Microsoft probably knows some trick on getting it to work well, but they have not documented it. So I say that you create your own interface that wraps the specifics of Win32 as much as possible. That way portability is somewhat achieved. Portable code is important, Win32 requires much tweaking and trial and much error before it works. May I suggest Linux as a more capable platform?

I do agree, but anoter thing is that I've been asked for writing an application for Win32... Its a little program for exchanging data over net w/o server or with server as only promoter for the offered content at the peers. And contens shoud not matter - must be described by XML annotation ...

M.N.