search

TBD54566975 / dwn-proxy-js

Apache License 2.0
1 stars 1 forks source link

28 interface nomenclature rather than direction #29

Closed KendallWeihe closed 1 year ago

KendallWeihe commented 1 year ago

https://github.com/TBD54566975/dwn-proxy-js/issues/28

FYI @michaelneale I didn't like the INBOUND vs OUTBOUND because there nothing to say that an incoming DwnRequest may not necessary bounce back out with an outbound DWN Message. Same with outbound, it's just a restful API, so there's no reason that it must necessary consist of an outbound DWN Message.

So rather than direction: INBOUND do an interface: DwnRequest

And then rather than direction: OUTBOUND do an interface: Restful

michaelneale commented 1 year ago

Not sure that is any clearer to me yet

KendallWeihe commented 1 year ago

Not sure that is any clearer to me yet

Yeah, in a way, to me it's less clear 😅 lol but... it's more true to the nature so I'm keeping it. Because like I said, there aren't any dedicated inbound/outbound prescriptions or functionality. Like, it's not impossible to have an "inbound" which also sends an "outbound" DWN Message... so idk, we're gonna run with it for now.