search

Comcast / sirius-reference-app

A reference application for getting started with Sirius
Apache License 2.0
5 stars 10 forks source link

Make the Java based application backend more interesting #12

Open tbarker9comcast opened 10 years ago

tbarker9comcast commented 10 years ago

The groovy example already uses a concurrent hash map as its backend. Maybe the java application can do something more interesting.

comcast-jonm commented 10 years ago

This is an interesting idea, if we can find a way to do this without over complicating the application. The main purpose of the reference app should be to illustrate how to hook a working application up to Sirius, and not much else. The simpler the sample application is itself, the more clearly it emphasizes the Sirius interfaces and dependencies.

From: tbarker9comcast notifications@github.com<mailto:notifications@github.com> Reply-To: Comcast/sirius-reference-app reply@reply.github.com<mailto:reply@reply.github.com> Date: Monday, February 17, 2014 at 4:30 PM To: Comcast/sirius-reference-app sirius-reference-app@noreply.github.com<mailto:sirius-reference-app@noreply.github.com> Subject: [sirius-reference-app] Make the Java based application backend more interesting (#12)

The groovy example already uses a concurrent hash map as its backend. Maybe the java application can do something more interesting.

— Reply to this email directly or view it on GitHubhttps://github.com/Comcast/sirius-reference-app/issues/12.

clinedome-work commented 10 years ago

@tbarker9comcast and I talked about maybe doing just a little indexing as an example. Could split keys on slash-delimited namespaces and index those. It'd be an easy addition that shows and example of a RequestHandler doing something slightly more interesting than just jamming the data in a map. It would also show that fetching from the built-up repositories is the right way to go, instead of using sirius.enqueueGet().