Closed GoogleCodeExporter closed 8 years ago
These are good suggestion for the future Enhancements for the "Action" part.
Hence scheduling this for the next release.
For this release, these kinds of things are supported through the Android
Application,
ravi.
Original comment by ravt...@gmail.com
on 25 Nov 2012 at 6:14
The design of 'ae' daemon and its monitors is considered one entity. If there
is a need for notification when say a monitor is down and before the 'ae'
daemon restarts that monitor, it is not the job of the 'ae' dameon itself but
the selfmon monitor. Add the label 'selfmon' and keep this as an enhacement.
Original comment by toddd...@gmail.com
on 25 Nov 2012 at 6:51
From design point of view, I can see that we can consider the case that if the
entire 'ae' system is down, how the user can be notified. One comes to mind is
that after the user is connected to 'ae' daemon via the aeProxy, the ae daemon
could send the keep alive message to user which can be an indicator for user to
find out whether the entire 'ae' system is down.
Original comment by toddd...@gmail.com
on 25 Nov 2012 at 7:31
The original bug report which calls for 'push' notification such as email is
not part of the design/architecture/implementation.
However, if the ae-daemon and monitors are dead, there should be a mechanism to
inform Android App. stating so. So, marking this as an enhancement,
ravi.
Original comment by ravt...@gmail.com
on 25 Nov 2012 at 7:36
Since the 'Push" feature is not part of the proposal of this project, we are
invalidating this issue,
ravi.
Original comment by ravt...@gmail.com
on 25 Nov 2012 at 7:59
Original issue reported on code.google.com by
prhamm...@gmail.com
on 24 Nov 2012 at 7:52