Inserts anObject into the runloop (and
retains it). anObject should implement
either the
<NetPort>
or
<NetObject>
protocols. Throws a
NetException if the class follows
neither protocol. After connecting
anObject, it will begin to receive the
methods designated by its respective protocol.
anObject should only be connected with
this after its transport is set.
Removes anObject from the runloop and
releases it. anObject will no longer
receive messages outlined by its protocol. Does
not close the descriptor of
anObject. anObject will
receive a
[<NetObject>-connectionLost]
message or a [<NetPort>-connectionLost]
message.
If any object should lose its connection, this will
automatically be called with that object as
its argument.
This is called to notify NetApplication that
aTransport has data that needs to be
written out. Only after this method is called will
aTransport begin to receive
[<NetTransport>-writeData:]
messages with a nil argument when it can write.
This protocol should be implemented by an object used in
a connection. When a connection is received by a
<NetPort>
, the object attached to the port is created and given
the transport.
Called when a connection has been established, and
gives the object the transport used to actually
transport the data. aTransport will
implement
<NetTransport>
.
Called when
[NetApplication -disconnectObject:]
is called with this object as a argument. This object will no longer receive data or other messages after it is disconnected.
Represents a class that acts as a port. Each port
allows a object type to be attached to it, and it will
instantiate an object of that type upon receiving
a new connection.
Called when a new connection has been detected by
NetApplication
. The port should should use this new connection to
instantiate a object of the class set by
-setNetObject:
.
A protocol used for the actual transport class of a
connection. A transport is a low-level object
which actually handles the physical means of
transporting data to the other side of the
connection through methods such as
-readData:
and -writeData:
.
Return YES if no more data is waiting
to be written, and NO otherwise. Used by
NetApplication
to determine when it can stop checking the transport
for writing availability.
Called by
NetApplication
when it is safe to write. Should return data read
from the connection with a maximum size of
maxReadSize. If maxReadSize
should be zero, all data available on the
connection should be returned.
This should serve two purposes. When data
is not nil, the transport should store the
data, and then call
[NetApplication -transportNeedsToWrite:]
to notify
NetApplication
that the transport needs to write. When
data is nil, the transport
should assume that it is actually safe to write
the data and should do so at this time.
NetApplication
will call
-writeData:
with a nil argument when it is safe
to write
Used for OS X compatibility. OS X does not have the
RunLoopEvents protocol. This is a
GNUstep-specific extension. This must be
recreated on OS X to compile netclasses.
Used for OS X compatibility. This type is an extension
to GNUstep. On OS X, a compatibility layer is created to
recreate the GNUstep extensions using OS X
extensions.