News for hackers. Stuff that matters.

A comment on Alan Kay on the misunderstanding of OOP (1998). Parent comment

Re:Alan Kay on the misunderstanding of OOP (1998) by ivan_gammel on Friday June 24, 2016 @08:41AM (#11969304)
HTTP is closer to RPC. You always know the address of the routine to call, so it's not actually a message (except in HATEOAS, in which you first need to learn the next address from last API call).

Closest analogy is the message queue (e.g. ESB) like Active MQ or Rabbit MQ (and the whole JMS tech), in which you do actually send a message and infrastructure does actually figure out who will receive and process it.

[ Parent | on HN ]
Re:Alan Kay on the misunderstanding of OOP (1998) by specialist on Friday June 24, 2016 @01:39PM (#11971809)
HTTP(S) is the opposite of RPC (meaning: message-based). Both SOAP and XML-RPC tried to remedy that.
[ Parent | on HN ]
Re:Alan Kay on the misunderstanding of OOP (1998) by ivan_gammel on Saturday June 25, 2016 @03:54AM (#11975606)
How exactly it is opposite?
[ Parent | on HN ]
Re:Alan Kay on the misunderstanding of OOP (1998) by specialist on Saturday June 25, 2016 @11:01AM (#11976523)
Difference between document (message-passing) and RPC styles:

http://stackoverflow.com/questions/9062475/what-is-the-diffe...

Replace SOAP with HTTP, since SOAP is just an ill-advised, unnecessary, redundant obfuscation layer on top of HTTP, and so contrast still applies.

[ Parent | on HN ]