home  wiki

Spelling: MWRPAdhocFrottleFlowcharts

These here are some flowcharts I've been working on that describe how
I think an OLSROLES, ILSE, OLSEN, OILS, OWLS, ELSE, ILSA, OLSON, ELSA, ELSI, ELSY, USSR, ALSO, OIL'S, OWL'S, OLA'S, OLE'S, AOL'S, AL'S, EL'S version of FrottleFettle, Brittle, Rattle, Throttle, Fritter, Prattle, Foretell, Fairytale, Brittler, Fertile, Frontal, Rattler, Fretted, Throttler, Frostily, Prattler, Futile, Rattly, Fondle should work.

Previously I've written that we should try to write a version of
FrottleFettle, Brittle, Rattle, Throttle, Fritter, Prattle, Foretell, Fairytale, Brittler, Fertile, Frontal, Rattler, Fretted, Throttler, Frostily, Prattler, Futile, Rattly, Fondle that works for any AdhocADC, Adham, Adj, Idaho, Idahos, Attic, Adhara, Adhere, Educ, OTC, Adage, Idaho's routing protocol - or no routing
protocol at all. I've since learnt a bit about OLSROLES, ILSE, OLSEN, OILS, OWLS, ELSE, ILSA, OLSON, ELSA, ELSI, ELSY, USSR, ALSO, OIL'S, OWL'S, OLA'S, OLE'S, AOL'S, AL'S, EL'S pluginsplug ins, plug-ins, polygons, plugs, plugging, polygon's, plains, plug's, pidgins, plunks, plaguing, penguins, ploughing, pluckiness, plunges, legions, plans, plungers, pidgin's, plucking, pagans, plucks, penguin's, legion's, Alcuin's, Pliny's, plan's, plunger's, Logan's, pagan's, Paulina's, Pauling's and have
decided that OLSR'sIlse's, Olsen's, Else's, Ilsa's, Olson's, Ilise's, Ilyse's, Elsa's, Elsi's, Elsy's, Alyse's, Elise's, Elsey's, Elsie's, Elyse's, Ilysa's, Elset's, Esra's, Osiris, Ulster's, Alisa's, Alysa's, Elisa's, Elora's, Ulcer's, Alsop's, Elbrus, Ulises, Alases, Ultras, Ulsters, Ulcers neighbor databases would be very handy to use.
Also, OLSROLES, ILSE, OLSEN, OILS, OWLS, ELSE, ILSA, OLSON, ELSA, ELSI, ELSY, USSR, ALSO, OIL'S, OWL'S, OLA'S, OLE'S, AOL'S, AL'S, EL'S seems to be streets ahead of other AdhocADC, Adham, Adj, Idaho, Idahos, Attic, Adhara, Adhere, Educ, OTC, Adage, Idaho's routing protocols
in terms of cross-platform implementation - so we don't lose much by
not supporting other protocols.

I believe a FrottleFettle, Brittle, Rattle, Throttle, Fritter, Prattle, Foretell, Fairytale, Brittler, Fertile, Frontal, Rattler, Fretted, Throttler, Frostily, Prattler, Futile, Rattly, Fondle OLSROLES, ILSE, OLSEN, OILS, OWLS, ELSE, ILSA, OLSON, ELSA, ELSI, ELSY, USSR, ALSO, OIL'S, OWL'S, OLA'S, OLE'S, AOL'S, AL'S, EL'S PluginPlug in, Plug-in, Plugging, Plaguing, Ploughing, Polygon, Plunging, Plucking, Plug, Kluging, Pluming, Plain, Plugs, Puling, Pidgin, Lugging, Plug's, Purging, Plunk, Pliny, Pulling, Splurging, Bulging, Penguin, Pulping, Pulsing, Pledging, Plunking, Pillaging, Plunge, Legion, Paging, Puking, Plan, Plunger may need to use a new type of Hello
packet - replacing the regular hello packet of regular OLSROLES, ILSE, OLSEN, OILS, OWLS, ELSE, ILSA, OLSON, ELSA, ELSI, ELSY, USSR, ALSO, OIL'S, OWL'S, OLA'S, OLE'S, AOL'S, AL'S, EL'S or the
LQ_hello packet of the ETXETC, TEX, EXT, ET, TX, EX, ETA, ETD plugin. Because FrottleFettle, Brittle, Rattle, Throttle, Fritter, Prattle, Foretell, Fairytale, Brittler, Fertile, Frontal, Rattler, Fretted, Throttler, Frostily, Prattler, Futile, Rattly, Fondle requires that all
packets be delayed until polled, the regular hello packets will
probalyprobably, provably, probable, probate, probity, proudly, parable, provable, prob, drably, pebbly, problem, probe, prole, prowl not work as they are sent at timed intervals

These flowcharts are a work in progress, but I think the reader will
get the gist of what I'm on about. The idea is closely based on the
ideas in these two papers:
http://www.eecs.berkeley.edu/~ergen/docs/wtrpiscc.pdf
http://faculty.cs.tamu.edu/welch/papers/icnp01.pdf
The main problem to overcome is that not every node is a neighbor of
every other node. So tokens need rules to be able to backtrack when
they hit a dead end. Nodes need to keep track of the node that passed
them the token - known as the predecessor, and of the node that they
will pass the token to - known as the successor. Also, a node may
receive a token more than once, so it may have more than one
predecessor and successor. The node needs to keep track of the order
of it's predecessor/successor pairs.

MAIN FUNCTION

RX FUNCTION

TOKEN FUNCTION

SOLICIT SUCCESSOR FUNCTION

[EditText] [Spelling] [Current] [Raw] [Code] [Diff] [Subscribe] [VersionHistory] [Revert] [Delete] [RecentChanges]

> home> about> events> files> members> maps> wiki board   > home   > categories   > search   > changes   > formatting   > extras> site map

Username
Password

 Remember me.
>

> forgotten password?
> register?
currently 0 users online
Node Statistics
building129
gathering196
interested489
operational241
testing200