BB to iPhone 4s - Thoughts Inside
-
-
I'm sure every smartphone can do the above.
If they enable editing forward for consumers, it would be enabled for business users as well. And even in the consumer space it leaves room for a mischief creator to falsify statements and then lay it on the door of the original sender.
I would like to know if the forward I receive has been edited or not. And also would like to ensure that any email I have sent cannot be forwarded after being edited.Last edited by sam_b77; 12-08-11 at 12:29 PM.
12-08-11 12:27 PMLike 0 -
- Highlight text body> copy> Compose new mail> Send To: Enter recipient name(s)> Paste Text> Click send.
I'm sure every smartphone can do the above.
If they enable editing forward for consumers, it would be enabled for business users as well. And even in the consumer space it leaves room for a mischief creator to falsify statements and then lay it on the door of the original sender.
I would like to know if the forward I receive has been edited or not. And also would like to ensure that any email I have sent cannot be forwarded after being edited.
Not everyone is a business user, and not all emails are business-related.
I don't hate that BlackBerry quirk. I just use my PC mail client to edit and forward those emails. However, it would be nice if I had the ability to edit and forward on the BlackBerry, so I didn't have to wait until I was using the PC.12-08-11 12:37 PMLike 0 - What you mentioned cannot be done if there are images in the body in addition to text. It also eliminates any HTML formatting of the text itself, since BlackBerry only composes in plain text.
Not everyone is a business user, and not all emails are business-related.
I don't hate that BlackBerry quirk. I just use my PC mail client to edit and forward those emails. However, it would be nice if I had the ability to edit and forward on the BlackBerry, so I didn't have to wait until I was using the PC.12-08-11 12:43 PMLike 0 - They definitely should at least allow you to delete the original sender info. There are many times when I want to forward information to someone but not send it with the original senders info (most times per the senders request). Also, if this can all be done on a PC anyways, why can't they allow it on a BB since we have the option to do this anyways?Laura Knotek likes this.12-08-11 12:58 PMLike 1
-
- I had enough of saying sorry to clients for call drop-outs, not to mention the lousy battery life.
A full year with iphone 4 and it's back to BB for me.
Even my Mother, a five year BB user in her 70's, went back to BB this week - 9900. And before anyone cracks an age gag she was a successful business woman.12-08-11 04:40 PMLike 0 - Well, if you don't use email much and don't care when you get emails, that's another story.
But BBs email is better because being pushed, and not fetch, I get it literally before I get it on the laptop. Not to mention the easiness of setup, security, etc.
The email on android and iPhone looks prettier for now, but it is nowhere near as RELIABLE, as BBs.12-08-11 06:37 PMLike 0 -
Google Sync for your phone12-08-11 07:31 PMLike 0 - That was the point but no one has a sense of humor here.
And btw, GMail is connected via AnctiveSync 24/7, as explained before, so its always in the "cloud", but its not real push.
The best part is that I am just repeating what you can find anywhere on the net, and yet everyone has to reply all arrogant and then gets offended if someone replies like you do... Ridiculous.
Posted from my CrackBerry at wapforums.crackberry.com12-09-11 01:13 AMLike 0 - That was the point but no one has a sense of humor here.
And btw, GMail is connected via AnctiveSync 24/7, as explained before, so its always in the "cloud", but its not real push.
The best part is that I am just repeating what you can find anywhere on the net, and yet everyone has to reply all arrogant and then gets offended if someone replies like you do... Ridiculous.
Posted from my CrackBerry at wapforums.crackberry.com
Wikipedia says two-way sync
Wikipedia also ultimately files it under Push Email
So, technically it's both. It pushes email directly to your device, but continuously syncs your data with their server, so you can see the same things (email, calendar, contacts, etc.) on any device that you choose to use.
Personally, that's the best way to do it: same thing on different screens while still benefiting from Push technology.
So to conclude:
The best part is that I am just repeating what you can find anywhere on the net, and yet everyone has to reply all arrogant and then gets offended if someone replies like you do... Ridiculous.12-09-11 02:17 AMLike 0 - I have mentioned in previous posts that GMail is "push" on android, but only BB has true push for all emails. This was the first argument some 12 pages ago. Then people decided to get arrogant and stop reading yet went on an all reporting spree, while I explained numerous times what every site says. Now, if you wanna categorize GMail as push, go ahead, but because your android device is always in "the cloud" of ActiveSync, is it real push? I don't think so...
And why are you guys getting so touchy, I'll never get it. Its a forum...
Posted from my CrackBerry at wapforums.crackberry.com12-09-11 02:25 AMLike 0 - Best part is that the first to start it all was Accidental Post, who called me "laughable" when it was totally uncalled for... Yet, I am the only one who gets reported for insulting and trolling... Some mods I tell ya...
Posted from my CrackBerry at wapforums.crackberry.com12-09-11 02:28 AMLike 0 -
Can I ask what the issue is with having push email also sync with information in the cloud?
Further, with Gmail, you're still getting new email pushed to your device as soon as it arrives, just like BB does with any email address; it just backs it up for you automatically, so again, having trouble seeing how this isn't real push technology.12-09-11 05:14 AMLike 0 - Can I ask what the issue is with having push email also sync with information in the cloud?
Further, with Gmail, you're still getting new email pushed to your device as soon as it arrives, just like BB does with any email address; it just backs it up for you automatically, so again, having trouble seeing how this isn't real push technology.
Here's how actyvesync works:
"A mobile phone that's configured to synchronize with an Exchange 2010 server issues an HTTPS request to the server. This request is known as a PING. The request tells the server to notify the device if any items change in any folder that's configured to synchronize in the next 15*minutes. Otherwise, the server should return an HTTP 200 OK message. The mobile phone then stands by. The 15-minute time span is known as a heartbeat interval.
If no items change in 15*minutes, the server returns a response of HTTP 200 OK. The mobile phone receives this response, resumes activity (known as waking up), and issues its request again. This restarts the process.
If any items change or new items are received within the 15-minute heartbeat interval, the server sends a response that informs the mobile phone that there's a new or changed item and provides the name of the folder in which the new or changed item resides. After the mobile phone receives this response, it issues a synchronization request for the folder that has the new or changed items. When synchronization is complete, the mobile phone issues a new PING request and the whole process starts over.
Direct Push depends on network conditions that support a long-standing HTTPS request. If the carrier network for the mobile phone or the firewall doesn't support long-standing HTTPS requests, the HTTPS request is stopped. The following steps describe how Direct Push operates when a mobile phone's carrier network has a time-out value of 13*minutes:
A mobile phone issues an HTTPS request to the server. The request tells the server to notify the device if any items change in any folder that is configured to synchronize in the next 15*minutes. Otherwise, the server should return an HTTP 200 OK message. The mobile phone then stands by.
If the server does not respond after 15*minutes, the mobile phone wakes up and concludes that the connection to the server was timed out by the network. The device reissues the HTTPS request, but this time it uses a heartbeat interval of 8*minutes.
After 8*minutes, the server sends an HTTP 200 OK message. The device then tries to gain a longer connection by issuing a new HTTPS request to the server that has a heartbeat interval of 12*minutes.
After 4*minutes, a new e-mail message is received and the server responds by sending an HTTPS request that tells the device to synchronize. The device synchronizes and reissues the HTTPS request that has a heartbeat of 12*minutes.
After 12*minutes, if there are no new or changed items, the server responds by sending an HTTP 200 OK message. The device wakes up and concludes that network conditions support a heartbeat interval of 12*minutes. The device then tries to gain a longer connection by reissuing an HTTPS request that has a heartbeat interval of 16*minutes.
After 16*minutes, no response is received from the server. The device wakes up and concludes that network conditions cannot support a heartbeat interval of 16*minutes. Because this failure occurred directly after the device tried to increase the heartbeat interval, it concludes that the heartbeat interval has reached its maximum limit. The device then issues an HTTPS request that has a heartbeat interval of 12*minutes because this was the last successful heartbeat interval.
The mobile phone tries to use the longest heartbeat interval the network supports. This extends battery life on the device and reduces how much data is transferred over the network. Mobile carriers can specify a maximum, minimum, and initial heartbeat value in the registry settings for the mobile phone."12-09-11 05:53 AMLike 0 - You can say BB email works more or less the same except the BIS server is doing all the hard work, the phone just sits and waits for the email to arrive which is true push.12-09-11 05:57 AMLike 0
- Accidental PostSlayer of MisinformationI have mentioned in previous posts that GMail is "push" on android, but only BB has true push for all emails. This was the first argument some 12 pages ago. Then people decided to get arrogant and stop reading yet went on an all reporting spree, while I explained numerous times what every site says. Now, if you wanna categorize GMail as push, go ahead, but because your android device is always in "the cloud" of ActiveSync, is it real push? I don't think so...
And why are you guys getting so touchy, I'll never get it. Its a forum...
Posted from my CrackBerry at wapforums.crackberry.com
I am done with you.
Sent from my MD276LL using Tapatalkjebulls likes this.12-09-11 06:38 AMLike 1 - Again, instant email does not equal push, stop kidding yourself, acticesync is nothing like Blackberry real push.
Here's how actyvesync works:
"A mobile phone that's configured to synchronize with an Exchange 2010 server issues an HTTPS request to the server. This request is known as a PING. The request tells the server to notify the device if any items change in any folder that's configured to synchronize in the next 15*minutes. Otherwise, the server should return an HTTP 200 OK message. The mobile phone then stands by. The 15-minute time span is known as a heartbeat interval.
If no items change in 15*minutes, the server returns a response of HTTP 200 OK. The mobile phone receives this response, resumes activity (known as waking up), and issues its request again. This restarts the process.
If any items change or new items are received within the 15-minute heartbeat interval, the server sends a response that informs the mobile phone that there's a new or changed item and provides the name of the folder in which the new or changed item resides. After the mobile phone receives this response, it issues a synchronization request for the folder that has the new or changed items. When synchronization is complete, the mobile phone issues a new PING request and the whole process starts over.
Direct Push depends on network conditions that support a long-standing HTTPS request. If the carrier network for the mobile phone or the firewall doesn't support long-standing HTTPS requests, the HTTPS request is stopped. The following steps describe how Direct Push operates when a mobile phone's carrier network has a time-out value of 13*minutes:
A mobile phone issues an HTTPS request to the server. The request tells the server to notify the device if any items change in any folder that is configured to synchronize in the next 15*minutes. Otherwise, the server should return an HTTP 200 OK message. The mobile phone then stands by.
If the server does not respond after 15*minutes, the mobile phone wakes up and concludes that the connection to the server was timed out by the network. The device reissues the HTTPS request, but this time it uses a heartbeat interval of 8*minutes.
After 8*minutes, the server sends an HTTP 200 OK message. The device then tries to gain a longer connection by issuing a new HTTPS request to the server that has a heartbeat interval of 12*minutes.
After 4*minutes, a new e-mail message is received and the server responds by sending an HTTPS request that tells the device to synchronize. The device synchronizes and reissues the HTTPS request that has a heartbeat of 12*minutes.
After 12*minutes, if there are no new or changed items, the server responds by sending an HTTP 200 OK message. The device wakes up and concludes that network conditions support a heartbeat interval of 12*minutes. The device then tries to gain a longer connection by reissuing an HTTPS request that has a heartbeat interval of 16*minutes.
After 16*minutes, no response is received from the server. The device wakes up and concludes that network conditions cannot support a heartbeat interval of 16*minutes. Because this failure occurred directly after the device tried to increase the heartbeat interval, it concludes that the heartbeat interval has reached its maximum limit. The device then issues an HTTPS request that has a heartbeat interval of 12*minutes because this was the last successful heartbeat interval.
The mobile phone tries to use the longest heartbeat interval the network supports. This extends battery life on the device and reduces how much data is transferred over the network. Mobile carriers can specify a maximum, minimum, and initial heartbeat value in the registry settings for the mobile phone."12-09-11 07:10 AMLike 0
- Forum
- Popular at CrackBerry
- General BlackBerry News, Discussion & Rumors
BB to iPhone 4s - Thoughts Inside
LINK TO POST COPIED TO CLIPBOARD