stateful versus stateless conditions exist in many technologies and applications... firewalls, dhcp, ipv6, programming, protocols, ad nauseum... it seems every one of these define stateful and stateless in their own inimitable way, and as it concerns its particular usage...
coming to terms with a useful definition that can encompass the whole is no easy task..
stateful: systems which track the state of the communication, protocol, event, instance or synchronization
stateless: no obligatory tracking of the state of communication, protocol, event instance or synchronization
one can make an analogy using the essential difference between udp and tcp
whereas udp is connectionless (stateless), tcp is connection oriented (stateful) because of built in reliability mechanisms
is this a stretch? i don't think so...
the advantage of a stateful state is a pre-determined guarantee at a cost of more overhead
the advantage of a stateless state is best effort with little reliance on resources
network cisco ccna gns3 certification arteq
a network runs through it
No comments:
Post a Comment