search

paulirotta / Tantalum

Tantalum Cross Platform Library
12 stars 6 forks source link

HttpPoster fix and Blackberry port initiation #44

Closed kingsleyadio closed 11 years ago

kingsleyadio commented 11 years ago

Fixed issue with the HttpPoster which wasnt working at all initially.

STARTED THE BLACKBERRY PORT. logging is working perfect as well as the caching. Still experiencing some issues with the networking (returning InterruptedIOException). The BB port depends on the JME RMS caching method for now as a temporary resort (in a way less flexible compared to the Blackberry's persistence storage). The native persistence would be incorporated once the networking is fixed. JME's logging approach is the preferred logging option (as stated clearly in the BB SDK docs), so it remains unchanged.

paulirotta commented 11 years ago

@adiksonline dude, let's skype tomorrow. You forked master before I merged in a major refactor, now we gotta choose the forward path. Don't want to make it difficult for you, want to see where you are on the BB line.

HttpPoster maybe is fixed in your line and the newly merged master...

kingsleyadio commented 11 years ago

Okay, so Iv been able to get a fix for the blackberry network problem. Apparently, It was working initially, but just needed me to add a few tweaks.

Yeah, skype cool!

kingsleyadio commented 11 years ago

Okay @paulirotta , Iv pulled the latest code, fixed all issues and updated it for the blackberry port as well. Merging shouldnt be a problem now I guess. There are still somethings I need to be clear about. Can we skype?

paulirotta commented 11 years ago

Automerge does not work, too many changes and issue appears fixed in master now. Let's start again as needed once BB and master are more synced.

bcombes commented 11 years ago

I took a lot at the blackberry port last week, it appears to crash arbitrarily whenever the device does not have any active network connections when used in applications that require some form of external connectivity. I haven't been able to trace out the issue yet, but I just thought to mention it here.

kingsleyadio commented 11 years ago

Never really experienced that. Anyway, Iv made some changes recently, and I will try issuing a pull request as soon as its in good shape. But then, are you experiencing this from the emulator or on a real device?

bcombes commented 11 years ago

I experienced it on both... I have a crash dump, but I haven't had time to analyse it just yet. Let me send that to you, it may be helpful in getting to the root of it. It did say something about accessing an 'unauthorized' api is all I can remember right now.

Hope this information is helpful

Bayo Puddicombe Pledge51 Ltd Tel: +234 8025011475 E-mail: bayop@pledge51.com Website: www.pledge51.com

_Winner of the _2012 ISPON Software Start-up of the Year Award

Note: Privileged/Confidential information may be contained in this message and may be subject to legal privilege. Access to this e-mail by anyone other than the intended is unauthorised. If you are not the intended recipient (or responsible for delivery of the message to such person), you may not use, copy, distribute or deliver to anyone this message (or any part of its contents ) or take any action in reliance on it. In such case, you should destroy this message, and notify us immediately. If you have received this email in error, please notify us immediately by e-mail or telephone and delete the e-mail from any computer.

The views, opinions, conclusions and other informations expressed in this electronic mail are not given or endorsed by Pledge51 unless otherwise indicated by an authorized representative independent of this message.

All reasonable precautions have been taken to ensure no viruses are present in this e-mail. However, Pledge51 cannot guarantee that e-mail communications are secure or error-free, as information could be intercepted, corrupted, amended, lost, destroyed, arrive late or incomplete, or contain viruses.

On Tue, Jun 4, 2013 at 4:12 PM, adiksonline notifications@github.comwrote:

Never really experienced that. Anyway, Iv made some changes recently, and I will try issuing a pull request as soon as its in good shape. But then, are you experiencing this from the emulator or on a real device?

— Reply to this email directly or view it on GitHubhttps://github.com/TantalumMobile/Tantalum/pull/44#issuecomment-18915717 .

kingsleyadio commented 11 years ago

Hi, I havent been working on the port lately, just resumed some a few days ago. So, I guess the problem with that is the blackberry specific connections (BES, BIS) getting called before the regular ones. So, if you are using an emulator, you might wanna start the MDS console first, so that the BIS connection can be emulated appropriately. On phone, you would need to have registered your app for the BIS permission . In the mean time, you should check out the latest update. I l try and add a way to specify the kind of connections you would like to use, so that it wont always default to the unavailable BIS/BES. I didnt get the crash dump you mentioned!