public class NoopPaxosApp extends java.lang.Object implements Replicable
Constructor and Description |
---|
NoopPaxosApp() |
Modifier and Type | Method and Description |
---|---|
java.lang.String |
checkpoint(java.lang.String name)
Checkpoints the current application state and returns it.
|
boolean |
execute(Request request) |
boolean |
execute(Request request,
boolean doNotReplyToClient)
This method must handle the request atomically and return true if
successful or throw an exception or return false.
|
Request |
getRequest(java.lang.String stringified)
Needed only if app uses request types other than RequestPacket.
|
java.util.Set<IntegerPacketType> |
getRequestTypes()
Needed only if app uses request types other than RequestPacket.
|
boolean |
restore(java.lang.String name,
java.lang.String state)
Resets the current application state for
name to state . |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
getMutualAuthRequestTypes, getRequest, getServerAuthRequestTypes
public boolean execute(Request request)
execute
in interface Application
public boolean execute(Request request, boolean doNotReplyToClient)
Replicable
execute
in interface Replicable
doNotReplyToClient
- If true, the application is expected to not send a response
back to the originating client (say, because this request is
part of a post-crash roll-forward or only the "entry replica"
that received the request from the client is expected to
respond back. If false, the application is expected to either
send a response (if any) back to the client via the
ClientMessenger
interface or delegate response
messaging to paxos via the ClientRequest.getResponse()
interface.request.getServiceName()
) altogether after a limited
number of retries, so the replica group may get stuck unless it
returns true after a limited number of retries. Thus, with paxos
as the replica coordination protocol, returning false is not
really an option as paxos has no way to "roll back" a request
whose global order has already been agreed upon.
With replica coordination protocols other than paxos, the boolean
return value could be used in protocol-specific ways, e.g., a
primary-backup protocol might normally execute a request at just
one replica but relay the request to one or more backups if the
return value of Application.execute(Request)
is false.
public java.lang.String checkpoint(java.lang.String name)
Replicable
checkpoint
in interface Replicable
Note that state
may simply be an app-specific handle,
e.g., a file name, representing the state as opposed to the
actual state. The application is responsible for interpreting the
state returned by Replicable.checkpoint(String)
and that supplied
in Replicable.restore(String, String)
in a consistent manner.
public boolean restore(java.lang.String name, java.lang.String state)
Replicable
name
to state
.
Note that state
may simply be an app-specific handle, e.g., a
file name, representing the state as opposed to the actual state. The
application is responsible for interpreting the state returned by
Replicable.checkpoint(String)
and that supplied in
Replicable.restore(String, String)
in a consistent manner.
restore
in interface Replicable
public Request getRequest(java.lang.String stringified) throws RequestParseException
NoopApp
for a more detailed example.getRequest
in interface AppRequestParser
Request
corresponding to stringified
.RequestParseException
public java.util.Set<IntegerPacketType> getRequestTypes()
NoopApp
for a more detailed example.getRequestTypes
in interface AppRequestParser