Agree etags would be good for tracking changes - in some ways regardless of integrated camel, but monitoring changes in resources from the outside is even more challenging.
On 1 October 2013 14:48, Saptarshi Purkayastha <sun...@gmail.com> wrote: > I would like to see Etags supported with our web API, if removing camel > The point is that then we can listen to the changes using ETags and check > modification for data when new ETags are generated for the same request. > Even shallow ETags would be a good first pass, if camel is removed. > > --- > Regards, > Saptarshi PURKAYASTHA > ------------------------------ > Date: Tue, 1 Oct 2013 11:26:55 +0100 > From: bobjolli...@gmail.com > To: dhis2-devs@lists.launchpad.net > Subject: [Dhis2-devs] Removing camel integration module > > > We have decided to remove the camel integration module from the dhis2 war > file in the next release. > > As the web api has matured it is now more feasible to run the likes of > apache camel or mule or similar software as external clients of the api. > > Regards > Bob > > _______________________________________________ Mailing list: > https://launchpad.net/~dhis2-devs Post to : > dhis2-devs@lists.launchpad.netUnsubscribe : > https://launchpad.net/~dhis2-devs More help : > https://help.launchpad.net/ListHelp >
_______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : dhis2-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
