Re: fgets() equivalent?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance


"Pops" <notreal@xxxxxxxxxxx> wrote in message
news:%23BehvDdNIHA.4656@xxxxxxxxxxxxxxxxxxxxxxx
Ben,

First, you need to stop attacking me. That is not your place as a MVP. You
are not the moderator.

I didn't attack you.

I have accepted at face value your claim that you've been working in this
field longer than I've been alive. I've assumed that you have a lot of
wisdom to share with the group. But so far your sharing has started a lot
of arguing and overall provided very little value to the question originally
asked. I'm trying to help, just as others have helped me when my postings
left (considerable) room for improvement.


If I said something incorrect, then don't attack me, but please correct it
with your terminologies. That is, if you know the answers. I will stress
that in no way did I ever say or implied or state "Cooked" and "Raw" are
standard terminologies. What makes you think I said or implied it was a
standard?

However, I will say it is WELL UNDERSTOOD concept for a very long time and
its applicable to many fields. If that is new to you, then you should not
attack people because you are ignorant of it.

Did you even read my message?

You didn't state that "Cooked" or "Raw" were standard, others did.
You challenged them to point to the standards, they pointed you to the
Single Unix Specification.

You are using the terms in non-standard ways and refuse to acknowledge the
existence of a standard. Perhaps it didn't exist when you started
working -- fine, don't refer to the standard in your own work, you seem to
do quite well without it. But do abide by the standard usage of the words
when communicating with others, or there will be nothing but confusion and
hard feelings all around.


As for the "layers", no, its NOT DATA FLOW. LAYERS!! Again, if you
disagree then show with TECHNICAL DETAILS what you think is correct.

Some time between when you went to school and when I did, they started
teaching this thing called the Open Systems Interconnection Basic Reference
Model which is the classic example of layering. Your example showed only
three layers. You demand technical details, here they are:

Your so-called "layers":

- client application
- sender device
- transmission
- receiver device
- server application

The "layers" the way everyone else has learned to see them and discuss them.

Transmission is the lowest layer shown, it deals with signalling, medium
reservation and contention, error detection, etc.
The sender and receiver device form the next layer up. They are both in the
same layer. Depending on whether you used the term in a hardware or
software sense, the interface protocol atop that layer might be the
interrupts and I/O ports or DMA buffers, or the OS hardware abstraction
layer for networking devices.
The client and server application are in the highest of the three layers,
dealing with interpretation of the data in some application-specific sense.


Again, if you want to contribute to the newsgroups, great, you were
obviously given MVP status - only god knows why. But even if deserving,
that doesn't make you any better than anyone else. So you NEED to STOP
attacking people and provide the answers if you think they are wrong,
again, that is if you know it. Otherwise shut up.

--
HLS



Ben Voigt [C++ MVP] wrote:
Again, that's a very convenient definition, and you are free to use
that if
you want, but that is NOT how the terms are used with Unix terminals.
"Cooked" and "raw" have a well-defined and well-established meaning in
Unix, and it is not the meaning you are attempting to assign.
Please keep in mind this is what we do. We write online and automated
hosting server and clients side applications that has dealt with this
issues for the past 25+ years and deal with customers across the board.

Which still doesn't make your terminology standard, it just means it
"works".

So please, there is no justice in trying to nit pick at generalizations
in a cyber space message world. Its a waste of your time and my time to
get into this nit picking mode. But I will try to outline for the
general reader who are keen to the concepts:

Regardless of the OS, in telecommunications, you have these five basic
layers:

- client application
- sender device
- transmission
- receiver device
- server application

Those aren't "layers" in current networking parlance. Blocks or stages
of data-flow, yes, but not layers. (You've actually listed items from
only three layers.)

Again, you've probably developed a nomenclature over the last three
decades that works well for you, but when you start discussing on a
newsgroup you really need to use the definitions that everyone else is
familiar with or can look up in the standard.


.

Relevant Pages

  • Re: fgets() equivalent?
    ... You on the other hand would rather NOT SHUT UP and rather ATTACK me, and that CERTAINLY does not have any value here. ... You don't need a STANDARD for that understanding. ... The "layers" the way everyone else has learned to see them and discuss them. ... The sender and receiver device form the next layer up. ...
    (microsoft.public.win32.programmer.kernel)
  • Re: Magic Flight: A New Public Key Algorithm stronger? than factoring
    ... attack to multiple layers. ... for all x,k1,k2 vectors of NUMTERMS integers mod FIELDMASK+1 ... This is I believe NOT implied by the linearity of layers, ...
    (sci.crypt)
  • Re: IJN and sound velocity profile
    ... layers to determine their attack or approach lane. ... I've never read that IJN subs were equiped with such a device or that IJN ...
    (sci.military.naval)
  • Re: Software Design With Layers
    ... > I am looking for opinions of and documentation suggesting suitable ... > layers, for use in development of a standard (console based) ...
    (comp.object)