Let's not use the term "release" - An apache release is when you build
tar/zip files for distribution. Anything in the repository is just
source code.
We have not yet made any release of the Java version. We can discuss
what changes we may want to make before the first Java version release.
Shanti
Binu John wrote:
The driver changes are required in the next release due to the fact
that we will be changing the application.
In the current version, we allow the application to be run in two
modes - A webapp mode in which most of the asynchronous components
(implemented as JMaki widgets) are disabled and the entire page is
generated at the server.
- An asynchronous mode in which a page is built using multiple JMaki
components. The JMaki components makes subsequent Ajax requests to
load the resources and render itself.
Even though the asynchronous mode is the default, we use the webapp
mode for performance testing since the async mode is not implemented
in the driver.
In the next release, we plan to expose all our services as proper REST
services, and the webapp mode will be eliminated. At this time, we
will need to modify the driver to mimic the asynchronous behavior of
the clients.
Thanks,
Binu
On 05/14/09 11:22, Kim LiChong wrote:
Typically, you would advertise the REST service via WADL/WSDL or even
just in a human readable format like HTML which could then be called
by any client whether it be a browser or not.
But if I understand your question correctly, are you asking if we
have to change the workload driver to use the rest interface? The
answer would be yes.
kim
In my understanding, you do not expose the rest interface to the
client (browser), do you? If so, these interfaces are just there as
a reference implementation but not used by the workload, right? Thanks.
-Akara
Kim LiChong (JIRA) wrote:
current REST based services are improperly implemented
-------------------------------------------------------
Key: OLIO-96
URL: https://issues.apache.org/jira/browse/OLIO-96
Project: Olio
Issue Type: Bug
Components: java-app
Reporter: Kim LiChong
Assignee: Kim LiChong
Currently, the REST based services for person and event do not have
unique URI as dictated by REST based architecture. Instead, they
are using parameter based GET or POSTS. Need to re-implement these
services with unique URI and other HTTP methods (eg. PUT, DELETE).
Will use Jersey based implementation of JSR-311 (JAX-RS)
