logo       

RE: IET does not handle Text Requestsafterentering FFP: msg#00138

Subject: RE: IET does not handle Text Requestsafterentering FFP
Hi Syed,

Am Donnerstag, den 16.02.2006, 16:35 +0530 schrieb
syed.khaleelulla@xxxxxxxxx:

> 
> The keys that can be exchanged are:
> InitiatorName

This one is marked as IO (initialize only) -> only during login

> TargetAlias

While it's marked as ALL (i.e. usage during FFP is allowed), it's a key
the target emits, so no need for the initiator to send a text request.
As IET doesn't make use of the Alias at the moment and I don't think
changing it at all during a normal session is an important use case, no
need for IET to send it, either. ;-)

> InitiatorAlias

Yep. But changing it during FFP isn't really useful, is it?

> TargetAddress
> TargetPortalGroupTag

Those are not sent by the initiator but part of the targets SendTarget's
response.

> SessionType

Nope, this one's marked as LO (leading only, i.e. login phase).

> And Vendor Extensions

Yep (although IET doesn't support any, so it would have to reject 'em
anyway).

Add MaxRxDSL to that and you've got the list of keys in my previous
mail ;-)

So do you really require support for changing MaxRxDSL/InitiatorAlias or
performing the SendTargets operation during a normal session's FFP?

Arne
-- 
Arne Redlich
Xiranet Communications GmbH



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642


<Prev in Thread] Current Thread [Next in Thread>