Hi Mircea,
There is absolutely no difference - to NK every identifer is an opaque token. It''s only your application, or the context of your architecture that imparts meaning to the identifiers.
res:/ is used around the place as the "house default" and if it has meaning is "a generic transport neutral resource".
xrl: if you see it would typically indicate that this identifier is probably defined within an XRL execution - but is essentially meaningless.
Hope this helps.
P.
There is absolutely no difference - to NK every identifer is an opaque token. It''s only your application, or the context of your architecture that imparts meaning to the identifiers.
res:/ is used around the place as the "house default" and if it has meaning is "a generic transport neutral resource".
xrl: if you see it would typically indicate that this identifier is probably defined within an XRL execution - but is essentially meaningless.
Hope this helps.
P.