Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is it HTTP or not? #27

Open
sagikazarmark opened this issue Jun 3, 2015 · 2 comments
Open

Is it HTTP or not? #27

sagikazarmark opened this issue Jun 3, 2015 · 2 comments

Comments

@sagikazarmark
Copy link

Hey @pmjones,

ADR is quite impressive, congratulations.

I especially liked the part which tries to compare ADR to other patterns.

One question came to my mind (and I am not a regular reddit reader, so I ask it here): ADR is web specific (replacement/refinement, whatever MVC). Does this also mean the responder (and routing BTW) should be HTTP specific?

Most MVC frameworks out there have HTTP specific foundation, which is fine, but in some cases it would be better to say Requests and Responses have nothing to do with HTTP. They CAN be from/sent to HTTP, but for internal requests, console requests HTTP makes no sense.

So my question: is ADR bound to HTTP?

Thanks in advance.

@pmjones
Copy link
Owner

pmjones commented Jun 3, 2015

is ADR bound to HTTP?

That's a really good question. I had not considered anything besides HTTP when I wrote the paper, since it was based on things I was seeing in HTTP-related applications.

However, I can see where it might be reasonable to say that ADR applies to client/server interactions, where a client sends a bundle/batch/package/collection of "request" information, and the server sends back a bundle/batch/package/collection of "response" information.

Does that help to answer your question?

@Nayte91
Copy link

Nayte91 commented Mar 26, 2020

Hi here,

I try to zoom out from your interesting proposition (as @sagikazarmark does with HTTP that's why I write here) and I think you aim to find the right way to organize anything with a Request/Response structure.

If I understand correctly, MVC is adapted to persistent logic : turn ON -> use it -> turn OFF. Times involved are generaly at human scale, like a desktop application, a video game, a football match, ...
ADR is a proposition adapted to an ephemere logic : request -> turn ON -> Logic -> response -> turn OFF. Times involved are at machine or process scale, where every day/sec/ms you wn is a clean win, like an HTTP request, an API call, a postal order in a paper catalog, ...
Am I right for this ?

If yes, so is your ADR good enough to organize any R/R behavior, like... SQL ? So in fine, can my cool ADR-website, polled by HTTP, poll my brand new ADR-database-FW by SQL ?
endif (sorry, dev joke)

Maybe I zoomed-out too much, BUT I feel like I need to give those thoughts to you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants