Is it worthwhile to re-examine the assumption that an individual should start at one end of the all-important "stack" and work their way to the other end?
As far as the process itself goes (although, all too often there's not a lot of process or method associated with design, but I'm sure we're all at least implicitly aware of that), I'm not sure that the undertakings on behalf of one layer can be as precisely isolated from one another as the data structures themselves. If the strategy adopted is bottom-up (thereby emulating many career paths), I'm not sure that one can tackle layer one decisions without an understanding of they type & volume of traffic they will be forced to contend with. For those of you who acknowledge data connectivity layers > 7, the unreasonable expectations & contradictory demands of the financial backers would probably need to be addressed first. Anyway, I'm just wondering if there exist advantages to working out of order; I'm well aware that certain advantages exist to working IN order . . FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
