over

presentation
http
business
logic
problem 1:
presentation depends on the interaction
flow, and mobile flows are really
different

presentation
http
business
logic
presentation
http
problem 2:
conversation state shared between client
and server. conversation state on
server leads to “session abuse”

presentation
http
business
logic
presentation
http
problem 2:
conversation state shared between client
and server. conversation state on
server leads to “session abuse”

presentation
http
business
logic
presentation
http
problem 2:
conversation state shared between client
and server. conversation state on
server leads to “session abuse”

n
io
presentation
t
http
a
s e
business
logic r t
e a
v t
presentation
n s
http
c o
problem 2:
conversation state shared between client
and server. conversation state on
server leads to “session abuse”

n
io
presentation
t
http
a
ap s e
pl business
logic
ic r t
e a
st at
v t
presentation
at io n s
http
e n
c o
problem 2:
conversation state shared between client
and server. conversation state on
server leads to “session abuse”

n
io
presentation
t
http
a
ap s e
pl business
r t
presentation
http
business
logic
presentation
http
e a
logic
ic
st at
v t
presentation
at io n s
http
e n
c o
problem 2: (sessions)
could make horizontal scalability harder
than it should be

n
io
presentation
t
http
a
ap s e
pl business
logic
ic r t
e a
st at
v t
presentation
at io n s
http
e n
c o
problem 2: (sessions)
it’s very hard to migrate conversations
from agents (mobile <-> desktop)

logic
business
business business
logic logic
usage usage
presentation presentation
problem 3:
http http
business logic usage is duplicated

business
logic
problem 3:
business business
logic logic
(duplication)
usage usage
presentation presentation
http http
worst when there’s an anemic domain model

presentation
presentation
http
business
logic
presentation
presentation
http
problem 4: rich client
more duplication (different languages),
more difficult to separate
responsibilities (where is what?)

presentation
business
http
usage
logic
business
logic
presentation
business
http
usage
logic
problem 5: (testability)
difficult to reach a particular point in
the conversation. presentation changes
often (smell: divergent change)

presentation
business
logic
http
presentation
adopted solution

SmartphoneClient.prototype.next = function() {
var self = this
this.seq(
this.purchase,
this.transferIn,
this.optIn,
this.waitForCompletion
).exit(function(exit) {
exit.callHandler(self.callbacks)
})
}
var client = new SmartphoneClient(server, {
onError: function(error) {
app.pages.notify.error(error)
},
onRoute: function(route) {
app.goTo(route)
},
onUrl: function(url) {
location.href = url
}
})

presentation
business
logic
http
presentation
clear separation
from application and
conversation state

presentation
business
logic
http
presentation
stateless: easy to scale
horizontally, conversations
can be migrated/resumed

$app->post("/purchase/:id/transfer-in/opt-in/pin",
function($purchaseId) use($app) {
ContentDelivery::on($app)
->process(function($request, $response) use($purchaseId, $app) {
$purchase = Purchase::fromRequest($request, $purchaseId);
$transferIn = $purchase->boundedTransferIn("pin-flow");
$transferIn->checkPin($request->params("pin"));
$response->status(200);
})
->rescue('OnebipCoreNotSupportedActionInState', 409)
->rescue('OnebipPurchasePurchaseNotFound', 404)
->rescue('OnebipPurchaseTransferInNotFound', 404)
->rescue('OnebipPurchaseSpendingLimitReached', 403)
->rescue('OnebipPurchaseCheckPinFailed', 400)
->rescue('HttpUnauthenticatedRequest', 401)
->deliver();
}
);
look, no session,
and the controller
code is really small

presentation
business
logic
http
presentation
clear application interface

$app->map("/purchases", ...
$app->get("/purchase/:id", ...
$app->post("/purchase/:id/login", ...
$app->get("/purchase/:id/buyer", ...
$app->post("/purchase/:id/transfers-in", ...
$app->get("/purchase/:id/transfer-in", ...
$app->put("/purchase/:id/transfer-in", ...
$app->post("/purchase/:id/transfer-in/opt-in/pin", ...
$app->put("/purchase/:id/transfer-in/mo", ...
clear application
interface

presentation
business
logic
http
presentation
testable

public function testShouldLoginWithARegisteredMsisdn()
{
$self = $this;
$msisdn = Baker::bake("Msisdn", "registered");
$purchase = Baker::bake("Purchase", "from Country", $msisdn->country());
$insertByUser = $msisdn->withoutNationalPrefixAsString();
$this->request("POST", "/purchase/{$purchase->id()}/login")
->withBody(array("msisdn" => $insertByUser))
->run(function($response) use ($self) {
$self->assertEquals(201, $response->status());
});
}
testable

business
logic
http
presentation
what
about presentation
old phones?

business
now
logic
http
presentation
http
presentation
presentation

namespace HttpFeaturePhone
{
class Client
{
public function next()
{
try {
$this->purchase();
$this->transferIn();
$this->optIn();
$this->waitForCompletion();
} catch (ClientExit $exit) {
$exit->callHandler($this->callbacks);
} catch (Exception $e) {
$exit = new ClientExit("error", $e->getMessage());
$exit->callHandler($this->callbacks);
}
}
...
}
} $client = new HttpFeaturePhoneClient($server, array(
"onError" => function($error) use ($app) {
$app->flash($error);
$app->redirectTo($app->urlFor("error-ui"));
},
"onRoute" => function($route) use ($app) {
$app->renderOrRedirectTo($route);
},
"onUrl" => function($url) use ($app) {
$app->redirectTo($url);
}
));

presentation
http
business
logic
http
presentation
presentation
tomorrow...

questions?