Hi
Any example of Akka as a RESTful service?
Thanks
navajyothi
--
>> Read the docs: http://akka.io/docs/
>> Check the FAQ:
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>> Search the archives: https://groups.google.com/group/akka-us
There are a couple of Activator templates. It's common to use Spray, which
is in the process of becoming Akka HTTP.
https://typesafe.com/activator/template/activator-akka-spray
On Tue, Oct 7, 2014 at 4:52 AM, naveen gayar wrote:
> Hi
>
>
> Any example of Akka as a RESTful service?
>
> Thanks
>
Hi,
If we want to use REST with akka persistence JAVA, what is recommended for
REST?
-Prakhyat M M
On Tuesday, 7 October 2014 20:06:51 UTC+5:30, rrodseth wrote:
>
> There are a couple of Activator templates. It's common to use Spray, which
> is in the process of becoming Akka HTTP.
>
> https:/
Once Spray is part of Akka as Akka HTTP I think they have a Java API
planned, but I don't know when that is due to be released. There are lots
of options for the web tier, including eg. Spring MVC and Play (which are
"full stack" frameworks, but can be used to build REST APIs).
On Thu, Oct 9, 2014
Akka-Http is already available as a preview and contains a Java API, here
is a link to the
docs:
http://doc.akka.io/japi/akka-stream-and-http-experimental/0.7/?_ga=1.231974623.1745281294.1365509340
The Akka Roadmap from August 28 stated that akka-http is planned to be
released for public review
Hi,
I am using Akka HTTP routes to define Akka HTTP REST end points.
Are there any guidelines that says "we should not use path param, and try
to use header", if yes in what all cases it should be followed?
for example a URI like /students/{state}/{dept} vs using using URI
/staudents and pa
I suggest you have a look at some guides about REST in general :) path
should be used to identify a resource, such as person/367 and
person/367/activity etc. headers are used for other things, but should not
really be for resource identification. Could be auth or similar things for
example.
--
Ko
