<div dir="ltr">Hi all,<div style><br></div><div style>With all the stuff going around the unified push, we started to look how to make the things easier for the developer to integrate "push" capabilities into his existing backend application.</div>
<div style><br></div><div style>After playing around and discussing with a few people, we came to the conclusion that these things are common, whatever your backend apps looks like : </div><div style><br></div><div style>
- You need the Java Sender Artifact</div><div style>- You need a Valid Unified Push Server URL</div><div style>- You need a valid Push Application ID</div><div style>- You need a valid Master Password to be able to interact with the unified Push Server </div>
<div style><br></div><div style>That seems to be the perfect case for a Forge Plugin : on any JEE application, you could apply the "Aerogear Push Plugin" that will do the current things : </div><div style><br></div>
<div style>- Pulls down the Java Sender Artifacts into your dependencies</div><div style>- Make available an Modle/JPA Config object with CRUD facilities on : Push server URL / Push Application ID / Master password.</div>
<div style><br></div><div style>This config object could be editable through :</div><div style>- Forge command line (i.e "aerogear-push set push-url "<a href="http://mypusherver.com">mypusherver.com</a>")</div>
<div style>- Through simple scaffolded User Interface</div><div style><br></div><div style>The idea is really to give people a "boost" when they want to enable "push" on their existing apps : i.e aerogear-push init >> pulls down the dependency , add the config object etc ...</div>
<div style><br></div><div style>Please comment on that, IMO this is really something that would reduce the step for someone who wants his apps to be "Push" aware.</div><div style><br></div><div style>Seb</div></div>