would engineer control api next-gen mars corsair calm instead an rpc?
forgive me verges being "discussion" question, nonetheless i unequivocally
appreciate yes/no answer, an suitable explanation.
suppose have settlement exercise control api robot, contend unbroken
generation mars rover. engineer api according calm
principles, model rpc, such xmlrpc?
i ask since i have something similar, nonetheless "robot" collection practical machines. i'm being urged rather impressive engineer, good famous rest advocate, api restful. i've never used rest principles, i'm struggling fit conceptualizing low-level inter-process apis. rest seems infused thesis interacting modifiable information repository, wholly hops away. i'm perplexing feels some-more closely determining robot. i remonstrate tough is, abstract, only information repository -- "put left turn", "put transport 100 meters", "get outmost temperature". nonetheless seems rather constructed model. i definitely accept advantage caching surrogate ("hello, jpl? akamai co-lo canberra. we're holding over corsair now, ok?")
so, calm settlement useful here? still aloft rpc even
when communication narrowly focused?
Comments
Post a Comment