Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
CODE PROJECT For Those Who Code
  • Home
  • Articles
  • FAQ
Community
  1. Home
  2. General Programming
  3. C / C++ / MFC
  4. Protocol Validation

Protocol Validation

Scheduled Pinned Locked Moved C / C++ / MFC
debugging
1 Posts 1 Posters 2 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • K Offline
    K Offline
    Kannan Ramanathan
    wrote on last edited by
    #1

    I have traces of a protocol (say a point-2-point data/control protocol) stored in files. I am thinking of writing a protocol validator, checking for the syntactic correctness as well as the semantic correctness (the correct flow as specified in the Spec). The checking rules are put in a separate file & the inference engine loads these rules and checks for the validity of the data (from the trace files). [rules file] + [trace file] ---(Inference engine)----> result This also has to be lean & fast. I am now doing a proto based on some ideas I have on how this can be done... but, I'd appreciate any ideas from you people on how this can be efficiently done (or how this is actually done :)). Thx

    1 Reply Last reply
    0
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • World
    • Users
    • Groups