raccoon-0.9.2: month wrong in /logs application

[_marv_]

When using the /logs URL provided with raccoon-0.9.2, the date shown is off by one month.
It shows 21/5/2007 when it should be 21/6/2007 (assumimg we do have june already ;-)

Marv

[jhnwkmn]

When using the /logs URL provided with raccoon-0.9.2, the date shown is off by one month.
It shows 21/5/2007 when it should be 21/6/2007 (assumimg we do have june already ;-)

You're right.

Hmm, interesting, that demo's been around for years now and you are the first one to point that out

But I'll fix that.

Johan

[_marv_]

Thanks Johan.

Is the "leave a message" link on bottom of the user's "Out-Of-Site" page supposed to work?

When using the gateway at http://www.at.openlaboratory.net:8080/<USERNAME> the link ist not there (probably it was removed), while when using a self compiled release the link is there, states "Message stored for later delivery" but the message gets never submitted.

I assume this is because of the "newer protocol" messages in Tomcat's logfile?

Pls. see:
http://discussion.forum.nokia.com/fo...d.php?t=110499

Could you put some light on these issues?

Thanks for your support,
Marv

[jhnwkmn]

Is the "leave a message" link on bottom of the user's "Out-Of-Site" page supposed to work?

No. It's one internal demo we have and apparently that link was included in the distribution.

The idea is, of course, that since mobile web servers cannot be assumed to be online all the time, the gateway can act as an intelligent intermediary. The queuing of messages for later delivery is one such activity, notifying users when a particular mobsite is online would be another.

Could you put some light on these issues?

I've been pushing Ferenc Dosa, who actually wrote the gateway and thus knows it the best, to respond, but he's been awfully busy lately

Stay tuned.

Johan

[ferencdr]

Hi,

it has been a while since I write that demo, and lately I've been busy with something entirely different things.

If I am not entirely mistaken, the "leave a message" should work in the OS distro.

1) The urls like http://john.doe.at.openlaboratory.ne...essageTextHere and http://john.doe.at.openlaboratory.ne...essageTextHere work in the phone.
2) the gw/webapps/messenger webapp is included in the gw distro - the "Leave a message" link should appear on the OutOfSight page only if the messenger webapp is deployed

One way to check that messages are indeed accepted for delivery is that after entering the message, but before going online with the mobsite, you check the content of the MySQL db (the one configured, the table is called MUSER_PROPS, methinks) if an appropriate message property entry is added. When going online, that entry is deleted, upon (possibly unsuccessful) delivery attempt.

The messenger webapp is one of the demos that is truly prototype in the sense that it's implementation is very insecure and has no real transaction semantics built in to the delivery. Just a demo... :-)

The delivery itself uses HTTP. That is, the component responsible for delivering messages simply issues an HTTP request, addressing the "appropriate" mobsite links. So if you can browse to the mobsite, this should work too.

Except, if for some reason, the URLs assumed are unavailable, like for instance when the real URLs used are not the ones assumed by the component. In your earlier post (http://discussion.forum.nokia.com/fo...d.php?t=110499) you mention that you have changed the URLs for the mobsite. The documentation for the messenger webapp also mentions similar problems.

Incidentally, soon I hope to be able to start contributing to the gw sources, and have some time to be able to do further development and stuff. Your feedback on the thread above wrt. the "weirdo" implementation is greatly appreciated - I am sorry to say that I had no time to study the tomcat API, the gw implementation was really meant to be a prototype (in fact, I overdid my mandate, since it is more-or-less usable enough already).

[_marv_]

Johan and Ferenc,

...
If I am not entirely mistaken, the "leave a message" should work in the OS distro.

Well, then is has to be a failure in my environment.

1) The urls like http://john.doe.at.openlaboratory.ne...essageTextHere and http://john.doe.at.openlaboratory.ne...essageTextHere work in the phone.

In fact, they do work on my side either. But of course they work only if the phone aka the user is "online". May I have a problem since I do not use the "http://<user>.at.system/" addressing scheme but "https://system/~<user>/" (or "@<user>/" in my case) scheme?

2) the gw/webapps/messenger webapp is included in the gw distro - the "Leave a message" link should appear on the OutOfSight page only if the messenger webapp is deployed

Well that is the case, all webapps (beside the ones for testing) are deployed to Tomcat.

One way to check that messages are indeed accepted for delivery is that after entering the message, but before going online with the mobsite, you check the content of the MySQL db (the one configured, the table is called MUSER_PROPS, methinks) if an appropriate message property entry is added. When going online, that entry is deleted, upon (possibly unsuccessful) delivery attempt.

Yes, the db entries are created as BLOB objects in the MUSERPROPS table (propname {inbox|instant}-msg, propval BLOB).
However they never get delivered to the phone.

The messenger webapp is one of the demos that is truly prototype in the sense that it's implementation is very insecure and has no real transaction semantics built in to the delivery. Just a demo... :-)

The delivery itself uses HTTP. That is, the component responsible for delivering messages simply issues an HTTP request, addressing the "appropriate" mobsite links. So if you can browse to the mobsite, this should work too.

Could it be that only the "virtual host" addressing scheme is supported here? That would explain why sendingt he postponed messages always fails. I cannot use the virtual host addressing scheme as we're forced to use SSL (https) and there are no named based virtual hosts with https allowed (certificate name errors, an "egg vs. chicken" problem).

Except, if for some reason, the URLs assumed are unavailable, like for instance when the real URLs used are not the ones assumed by the component. In your earlier post (http://discussion.forum.nokia.com/fo...d.php?t=110499) you mention that you have changed the URLs for the mobsite. The documentation for the messenger webapp also mentions similar problems.

What problems do you mention specifically? I really read all documentation reg. the webapps, may be I missed something?

Incidentally, soon I hope to be able to start contributing to the gw sources, and have some time to be able to do further development and stuff. Your feedback on the thread above wrt. the "weirdo" implementation is greatly appreciated - I am sorry to say that I had no time to study the tomcat API, the gw implementation was really meant to be a prototype (in fact, I overdid my mandate, since it is more-or-less usable enough already).

Well, for a proof-of-concept demo it looks rather mature and stable. I had no stability issues or hangups, it is just "it works every time or it does not work at all", which is far superior to most of the demos I've been dealing with so far.

Thank you for your work!
Greetings,
Marv