Bug 3126 - RFT resource reference property TransferKey is poorly named
: RFT resource reference property TransferKey is poorly named
Status: ASSIGNED
: RFT
RFT
: development
: PC Linux
: P3 trivial
: 4.2
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2005-04-10 13:14 by
Modified: 2005-04-11 14:15 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2005-04-10 13:14:12
Since an RFT resource applies to an entire request, the resource reference
property "TransferKey" is poorly named.  This is confusing since it makes it
seem like a resource is tied to an individual transfer within some request.  I'd
recommend changing it to RequestKey or something.  This isn't a huge deal (thus
the "trivial" severity of the bug report), but it can cause trouble when trying
to debug using SOAP messages and RFT-specific logging which contains both a
request ID and a transfer ID.  One would expect TransferKey to match one of the
trasnfer IDs, but instead it matches to a request ID.
------- Comment #1 From 2005-04-10 21:56:29 -------
this change would be an interface change so set to 4.2