Garrett D'Amore writes: > > I don't think that makes sense. At a minimum, I think we're lacking > > some archtecture here. > > > > I don't know about those. I was just offering a data point.
OK; thanks. It does offer an additional point of trouble, in that there could be drivers that support simultaneous operations without trouble, others that exclude simultaneous command-type operations but have no problem scanning while already connected, and still others that are incapable of scanning while in connected state. For what it's worth, we don't bother scanning if we're already connected and the connection appears to be solid, but there's no specific lock-out between scan and connect -- nor was there in the previous Phase 0 code, nor can there be any such lock-out in the application itself as long as dladm(1M) exists. > It does > sound like there is indeed some architecture missing. *sigh* -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list [email protected]
