>The way to decide on a new code is what fits best the Windows >environment and not what should be done to enable interoperability >between Windows and Linux. As I see it, this is the way to go.
I agree that the implementation should be what best fits into the Windows environment. Interoperability is a wire protocol issue, and should absolutely work, regardless of whether the remote side is running Linux, Solaris, or a vendor stack. If the implementation does not interoperate, it needs to be fixed. >This is an open source project, and it was so long before you have start >to review the code. To be clear, I've been on this mailing list for a couple of years, and have actually looked at a lot of the code that's been posted to the list. However, since Fab moved to Microsoft, very little code has found its way onto the list. I appreciate that the patches will be posted to the list in the future, but even discussions of direction need to be done on the list. Potential customers aren't likely to call into a working group meeting. - Sean _______________________________________________ ofw mailing list [email protected] http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw
