Home » Eclipse Projects » DSDP - Target Management » TCF communication protocol versioning
| TCF communication protocol versioning [message #33230] |
Thu, 12 March 2009 10:31  |
Eclipse User |
|
|
|
What is the version of the TCF communication protocol specified in
http://dsdp.eclipse.org/dsdp/tm/tcf/docs/TCF%20Specification .html ?
Is there a way, or planned a way, to have versioning as part of the
protocol itself? For example, it could be possible for the PC side to
request the target for the version used.
Or the target could be allowed to use various versions of the procotol in
parallel, and the PC side would know, for example by looking at the
message header, which version the message belongs to. This would make
really good sense if different parts of the target is delievered from
different vendors, each implementing different versions of the protocol
(you can't expect everyone to upgrade at the same time).
|
|
|
| Re: TCF communication protocol versioning [message #33371 is a reply to message #33230] |
Thu, 19 March 2009 08:53  |
| Eclipse User |
|
|
|
Hi Thomas,
there is a plan to version the TCF Protocol Specification in a
fine granular way. Felix Burton has the action item to do that:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=269352
I just created the bug for tracking the effort, but we did discuss it on
the TCF Round Table meeting recently:
http://wiki.eclipse.org/DSDP/TCF/Meetings/March_12_2009_Roun d_Table
Cheers,
--
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
Thomas Emil Hansen wrote:
> What is the version of the TCF communication protocol specified in
> http://dsdp.eclipse.org/dsdp/tm/tcf/docs/TCF%20Specification .html ?
>
> Is there a way, or planned a way, to have versioning as part of the
> protocol itself? For example, it could be possible for the PC side to
> request the target for the version used.
>
> Or the target could be allowed to use various versions of the procotol
> in parallel, and the PC side would know, for example by looking at the
> message header, which version the message belongs to. This would make
> really good sense if different parts of the target is delievered from
> different vendors, each implementing different versions of the protocol
> (you can't expect everyone to upgrade at the same time).
>
|
|
|
| Re: TCF communication protocol versioning [message #579831 is a reply to message #33230] |
Thu, 19 March 2009 08:53 |
| Eclipse User |
|
|
|
Hi Thomas,
there is a plan to version the TCF Protocol Specification in a
fine granular way. Felix Burton has the action item to do that:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=269352
I just created the bug for tracking the effort, but we did discuss it on
the TCF Round Table meeting recently:
http://wiki.eclipse.org/DSDP/TCF/Meetings/March_12_2009_Roun d_Table
Cheers,
--
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
Thomas Emil Hansen wrote:
> What is the version of the TCF communication protocol specified in
> http://dsdp.eclipse.org/dsdp/tm/tcf/docs/TCF%20Specification .html ?
>
> Is there a way, or planned a way, to have versioning as part of the
> protocol itself? For example, it could be possible for the PC side to
> request the target for the version used.
>
> Or the target could be allowed to use various versions of the procotol
> in parallel, and the PC side would know, for example by looking at the
> message header, which version the message belongs to. This would make
> really good sense if different parts of the target is delievered from
> different vendors, each implementing different versions of the protocol
> (you can't expect everyone to upgrade at the same time).
>
|
|
|
Goto Forum:
Current Time: Tue May 27 15:38:46 EDT 2025
Powered by FUDForum. Page generated in 0.02223 seconds |
Home