Originally posted by Mark Spritzler:
Ahh, now the requirements come to light. Thanks Alfredo.
OK, so it is all about online vs offline. So here is the design. You need to have the client not know whether it is calling a Servlets, a Plain Old Java Object, or an EJB. It only knows how to call methods on a simple interface. The implementations of this interface is what will know whether it is calling a Servlet, Plain Old Java Object, or EJB. So these implementation will convert the response received from the Servlet, POJO, or EJB, into a format that the client can use. This way we have extracted out the need for the client to care whether it is working online or offline...
Building Blockchain Apps: https://www.buildingblockchainapps.com/
Rust and WebAssembly on the server-side: https://www.secondstate.io/ssvm/
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
James Carman, President<br />Carman Consulting, Inc.
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime. |