Dude, this is the future and you're on the right track. But go big, or go home. The right solution includes all push(XMPP,SIMPLE,...)/pull(email,RSS,...) protocols supported by a personal proxy/server that makes one tunneled dynamic push connection to the mobile device.
Start with a big picture and modify it for a better personal/mobile experience:
The Kamailio SIP server ties in nicely with jabberd2 to provide a very good starting point, and they both already run on sub-$50 OpenWRT devices.
Dude, this is the future and you're on the right track. But go big, or go home. The right solution includes all push(XMPP,SIMPLE,...)/pull(email,RSS,...) protocols supported by a personal proxy/server that makes one tunneled dynamic push connection to the mobile device.
Start with a big picture and modify it for a better personal/mobile experience:
<snip>
The Kamailio SIP server ties in nicely with jabberd2 to provide a very good starting point, and they both already run on sub-$50 OpenWRT devices.
So you are basically recommending a server that can handle all kinds of different content, and then push it to the device? Something similar to the push api for android devices). This is something that I have always felt was missing from maemo.
This service could possibly grow into something like this, but for now I plan on making it extendable, and adding features as requested.
An all inclusive push api for the device would best be setup by nokia themselves.
What about the name JPush (for jabber push)? This is tied to the protocol used, but I can't think of anything better.
I have been researching along these lines lately as well, trying to be more 'real-time'
I think for me is going to end up being some combination of xmpp(ejabberd) for the pushing and amqp(rabbitmq) for the brokering, proxying, queuing whatever you wanna call it
google it and find some intersting projects along these lines already under way for a while
I have been researching along these lines lately as well, trying to be more 'real-time'
I think for me is going to end up being some combination of xmpp(ejabberd) for the pushing and amqp(rabbitmq) for the brokering, proxying, queuing whatever you wanna call it
google it and find some intersting projects along these lines already under way for a while
I really would prefer to stay away from anything that requires my device to maintain yet another connection to the internet, and eat up more of my battery. This is able to use an existing xmpp connection, which I don't think anything else is able to do.
I am having issues with the following command sending / receiving new emails if I completely disable polling. If I set it to check for new messages every 24 hours or less, it works fine. If anyone has a chance, could they try running this command with automatic polling disabled, and see if it actually checks for new messages?:
I really would prefer to stay away from anything that requires my device to maintain yet another connection to the internet, and eat up more of my battery. This is able to use an existing xmpp connection, which I don't think anything else is able to do.
I am having issues with the following command sending / receiving new emails if I completely disable polling. If I set it to check for new messages every 24 hours or less, it works fine. If anyone has a chance, could they try running this command with automatic polling disabled, and see if it actually checks for new messages?:
How do you define actions, etc on the client side for stuff being pushed to the client? I'll have to take a deeper look at rabbitmq, and see if it would work better.
