Implementations of Lotus Traveler works great on Android phones with the exception of one issue that we have discovered. Attachments! If you want to forward an email with an attachment, you must download the attachment first and then reattach the attachment to the message that you are forwarding. If not, the attachment will not be included. This has become an issue with a CEO of one of our clients who moved off his Blackberry and discovered that his attachments are not forwarding. Lotus Traveler seems to work like Notes in that it need to download the attachment before it forwards the message. This is not a good idea since handheld devices have limited bandwidth and memory. It is not even a good idea for Notes. IBM need to change this. Blackberry devices only include a pointer to the attachment and not the attachment itself so that when you forward a message with an attachment the server takes care of rest. This is critical when you have large attachments. As a result, the CEO is moving back to the Blackberry.
After my last post in this series -- way back in September 2022, several things happened that prevented any further installments. First came CollabSphere 2022 and then CollabSphere 2023, and organizing international conferences can easily consume all of one's spare time. Throughout this same time period, our product development efforts continued at full speed and are just now coming to fruition, which means it is finally time to continue our blog series. So let's get started... As developers, most of us create applications through the conscious act of programming, either procedural, as many of us old-timers grew up with, or object-oriented, which we grudgingly had to admit was better. This is true whether we are using Java, LotusScript, C++ or Rust on Domino. (By the way, does anyone remember Pascal? When I was in school, I remember being told it was the language of the future, but for some reason it didn't seem to survive past the MTV era). But in the last decade, there a
Comments
If you forward or reply to messages that is truncated, its the truncated msg that is sent. So the received end of the user is nto getting the whole history.
I reported the issue with IBM, but it came on a "if enough people complain about it, we might do something with it" list.