[ofw] API breakage in trunk

[James Yang]

Since this is the last field in the structure. Old application does not know it and will not use it, how will it create problem for them? Any example?

Thanks,
James

-----Original Message-----
From: ofw-bounces at lists.openfabrics.org [mailto:ofw-bounces at lists.openfabrics.org] On Behalf Of Sean Hefty
Sent: Friday, February 19, 2010 8:37 AM
To: 'Tzachi Dar'; 'ofw_list'
Subject: Re: [ofw] API breakage in trunk

>Why is this such a big problem?

You're kidding, right?

>This is a new release and we can ask for application to be recompiled.

No - we can't ask applications to just be recompiled.  This assumes that the
user has the ability to recompile, application release cycles are tied to OFA
release cycles, and the user has the ability to move their application forward.

When you upgrade from one version of Windows to another, do you automatically
buy all new applications?

>I'm quite sure that a similar solution was created for Linux.

IBoE has not been accepted upstream or into the official user space libraries.
Linux allows kernel interfaces to change between releases.  User space APIs and
ABIs absolutely try to avoid breaking existing applications.  This change
affects user space applications.

_______________________________________________
ofw mailing list
ofw at lists.openfabrics.org
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw