K
Ken Allen
I am interested in developing an iSCSI target component, but instead of
writing it as a device driver, I wish to implement it as a Windows service
developed in .Net (and C#). I understand that Microsoft provides an iSCSI
client, but they do not provide the target code at all. Basically my iSCSI
target service, at least in the first version, will simply direct the I/O
requests to a local disk partition, permitting the iSCSI protocol to be used
to access a remote partition, rather than the Windows 'share' mechanism.
I need information on how a .Net/C# service could define itself as an iSCSI
target and then ensure that it receives the packets from any iSCSI client
that connects to it. I have the iSCSI protocol document, but it is a bit
vague in this area.
-ken
writing it as a device driver, I wish to implement it as a Windows service
developed in .Net (and C#). I understand that Microsoft provides an iSCSI
client, but they do not provide the target code at all. Basically my iSCSI
target service, at least in the first version, will simply direct the I/O
requests to a local disk partition, permitting the iSCSI protocol to be used
to access a remote partition, rather than the Windows 'share' mechanism.
I need information on how a .Net/C# service could define itself as an iSCSI
target and then ensure that it receives the packets from any iSCSI client
that connects to it. I have the iSCSI protocol document, but it is a bit
vague in this area.
-ken