Hi all,

�I am *experimenting* with the replacement of the current network layer with OCEAN.

�My current plan is to make Zinc tests green while working on the top of OCEAN.

�And investigate the removal of all the current Network classes (does it play?).

�After looking at Zinc code, there are few dependencies.

�Basically, I implemented an OCNSOcketStream (inheriting from SocketStream) and redefined some methods of ZnNetworkingUtils.

�It seems to play so far (green tests).

�But then, I discovered that Zodiac introduces a new SocketStream hierarchy (ZdcAbstractSocketStream).

�Now remember the mails of Sven.

�So my questions are:

1) Is the intent of ZdcSocketStream to be a future replacement for SocketStream?

2) why �ZnNetworkingUtils>>initialize makes use of SocketStream instead of ZdcSocketStream?

why the code isn't something like that:

ZnNetworkingUtils>>initialize

super initialize.

self socketStreamClass: �(Smalltalk globals at: #ZdcSocketStream ifAbsent: [ SocketStream ]) .

self secureSocketStreamClass: (Smalltalk globals at: #ZdcSecureSocketStream ifAbsent: [ nil ])

Moreover, I guess that ZdcSocketStream should speed up things (it says optimized version in the name of the superclass ;-)).�

So probably, my OCNSOcketStream should better inherit from ZdcSocketStream.

Thanks for giving me some light here,

Luc