Re: ebme report

David Brown N2RJT <[email protected]> Mon, 5 Jul 2004 11:20:11 -0700 (PDT)
Newsgroups gmane.network.everybuddy.devel
Message-ID <[email protected]>
Hi y'all!
I would indeed like to try to debug the HTTP transport.
Where can I get the EBME source and gateway software?
-- 
Dave Brown <[email protected]>

On Tue, 22 Jun 2004, Meredydd wrote:

> On Tuesday 22 June 2004 06:11, you wrote:
> > Meredydd,
> > I have tried ebme.jar on my Sony Ericsson T610 with T-Mobile service
> > in USA. The phone doesn't support sockets, but I get a connection
> > with WAP.
> Oh, wow. Someone to help me debug the HTTP transport. Fantastic!
>
> If you're doing that, you'll also probably want a copy of the gateway
> software. I'll get that and the EBME source to you asap.
>
> By the way, those usability wotsits you reported to me a while back went
> onto my list-o-things-to-fix, and I should be putting out a proper
> release of ebme, with these fixes in, once we get the HTTP stuff ironed
> out.
>
> > I have configured my eb-lite core for one AIM account with one buddy,
> > just to try this out in a limited way.
> OK, but just asking - has it been connected first? Try it with a
> connected account first...
>
> > The first time I try to connect, after I answer the "Allow Web
> > Access" query, the phone screen says "Connecting... Connecting Please
> > wait while Everybuddy connects..." and then after about 10 seconds
> > the
> > GPRS/WAP/whatever icon goes away. After 5 minutes, no change.
> Now that's exceedingly odd. Looks like something's up with the HTTP
> transport.
>
> > The core logs the following:
> >
> > Incoming connection
> > Accepted cookie
> > Got 2 parameters:  html_strip 1
> > Got 2 parameters:  message_capable 0
> > Got 1 parameters:  list_services
> > Got 1 parameters:  list_local_accounts
> > Got 1 parameters:  list_contacts
> > Got 1 parameters:  get_held_messages
> That just means the gateway got the session-initialise message from the
> phone, made a connection, and did its initial automatic setup. I think
> we'll need to look at the WAP traffic for further info.
>
> > Read 0 chars
> That's it disconnecting, I think.
>
> > Then, I exit the application (sign off), and try again.
> > The core server logs the same stuff, and then ebme crashes.
> > The phone reports an error: "The application consumes too much
> > memory."
> Wibble. That'll be a phone bug, I think. Most phones eradicate any trace
> of a Java app from memory on killing it (Nokias certainly do), so I
> think that'll be a phone bug. I'll check whether I'm leaving any
> persistent threads knocking around, but I don't think I am.
>
> > Incoming connection
> > Accepted cookie
> > Got 2 parameters:  html_strip 1
> > Got 2 parameters:  message_capable 0
> > Got 1 parameters:  list_services
> > Got 1 parameters:  list_local_accounts
> > Got 1 parameters:  list_contacts
> > Got 1 parameters:  get_held_messages
> > Read 0 chars
> Once again, that's the gateway's initial setup routine, followed by
> zilch. You'll want to debug the phone <=> gateway connection.
>
> > I'll have to run sysinfo from the midlet.org site to see how much
> > memory the phone has. The phone's memory utility says it has over
> > 900M free, but that might not all be available for J2ME.
> It quite frequently is, actually. Anyway, ebme should never run out of
> memory - in emulator tests, it stays within 64k, which is the most
> conservative memory barrier I've ever encounteres.
>
> > If the phone's not too limited, I'd like to try to debug this.
> > Could I perhaps get the source for EBME?
> Sure thing.
> > Also, any advice or hunches you have would help.
> Get the HTTP transport source. I'll put both up for download and mail
> you in a bit.
>
> Also, do you mind if we move this to the Everybuddy mailing list? This
> is getting big and technical, and it would be nice if our conversation
> were public, so other people can see and help too.
>
> Meredydd
>
>
> PS - I'm sorry, I'm talking to a lot of people about ebme, but are you
> the one with the Treo? If so, could you start another thread on the
> mailing list discussing how to get that working?
>

--
Dave Brown <[email protected]>