[00:21] *** eikenberry has joined #kamaelia

[04:02] *** salmon_ has joined #kamaelia

[06:04] *** Uraeus has joined #kamaelia

[07:00] *** Uraeus has joined #kamaelia

[08:02] *** MS- has joined #kamaelia

[13:42] *** eikenberry has joined #kamaelia

[15:14] *** salmon_ has joined #kamaelia

[15:23] < MS-> Monthyly tarball for august - 0.9.8.0 has been uploaded. It's not a huge delta from 0.9.7.0

[15:23] < MS-> Most effort this month has been expended on trying to get one of JMB's branches into a state it can be merged.

[15:26] < MS-> I did however add this component to /trunk because I really needed it in a project at work:

[15:27] < MS-> http://code.google.com/p/kamaelia/source/browse/trunk/Code/Python/Kamaelia/Kamaelia/Apps/MPS/TPipe.py

[15:29] < MS-> Delta against 0.9.6.0 though is pretty large though

[16:30] < MS-> Yay, I can now get part of JMB's system working.

[16:31] < MS-> Trying to figure out what messages like:

[16:31] < MS-> DEBUG/kamaelia.publish.gateway.interface: kamaelia.testing@googlemail.com/headstock-3DDD4B04 available.

[16:31] < MS-> mean

[16:43] < MS-> On the upside I can see messages going *from* a google chat window to the kamaelia publish process, and then falling on the floor

[16:43] < MS-> Not sure why messages *from* kamaelia publish aren't reaching the google talk/chat client

[17:05] < MS-> OK, now I can see how headstock receives messages, which is a start

[17:14] < MS-> OK, going back to basics, I can now use headstock's simplechat example to send messages back and forth

[17:14] < MS-> which is a good start

[17:22] < MS-> OK, looks like jason's code is correctly making a headstock message. I think

[17:39] < MS-> OK, it looks like jason's code very nearly passes it's message onto headstock...

[17:40] < MS-> ("webhandler", "xmpp.outbox"): ('msgdisp', 'forward') Seems to be where some stuff is happening...

[17:41] < MS-> So it passes it onto the "forward" inbox of this:

[17:41] < MS-> msgdisp = MessageDispatcher(),

[17:42] < MS-> Which comes in here:

[17:42] < MS-> from headstock.protocol.core.message import MessageDispatcher, MessageEchoer

[17:42] < MS-> OK, so far so good

[17:42] < MS-> I can now trace a request through from jason's code through to code that I know works

[17:43] < MS-> So clearly, jason's code is doing something that the MessageDispatcher doesn't like

[17:44] < MS-> OK, so far so good

[17:58] < Lawouach> *hmm

[17:58] < Lawouach> sorry MS- I was away, if you're using the latest headstock trunk, that'll probably won't work

[17:59] < Lawouach> Things have changed quite a bit

[17:59] < Lawouach> Unfortunately, Jason had to use the very early API which has been quite improved since then

[17:59] < MS-> That's fine. I've got a working version of simplechat, and a nearly working version of Jason's code. I think I can probably adapt one to talk to the other :-)

[17:59] *** MS- nods

[17:59] < Lawouach> oh nice

[17:59] < Lawouach> so things haven't changed that much then

[17:59] < Lawouach> well if simplechat works

[17:59] < Lawouach> you've got the core working fine

[18:00] < Lawouach> that's cool

[18:00] < MS-> Ah, no simplechat from your current headstock works

[18:00] < Lawouach> ping me back tomorrow if you can, I'll have more time

[18:00] < Lawouach> MS-: right-o

[18:00] < MS-> But the thing that gives me some hope is that his code is able to use your code to log in correctly

[18:00] < MS-> and can receive messages

[18:00] < Lawouach> right

[18:00] < MS-> which is a huge amount of the battle done :-)

[18:00] < Lawouach> then that's enough

[18:00] < Lawouach> yeap

[18:01] < Lawouach> the rest of headstock is just other xmpp extensions

[18:01] < Lawouach> and a new api that Jason couldn't use at the time as it didn't exist :)

[18:01] < Lawouach> headstock needs a massive refactoring but it'll do for now

[18:03] < MS-> :-)

[18:03] < MS-> I'd noticed there'd been a fair amount of change :)

[18:04] < MS-> I suspect what's going wrong is that Jason's just creating "Wrong" messages.

[18:04] < MS-> Or rather his code is

[18:04] < MS-> I think he wants to stay away from the code as much as he can :-)

[18:04] < Lawouach> :)

[18:06] < Lawouach> does it mean you can't process those messages?

[18:08] < MS-> Essentially, I've traced through his code, and found that his messages are reaching the MessageDispatcher correctly - which is good, so they just need adapting to be correct.

[18:08] < MS-> On the flip side messages coming in are also reaching his code in the right place

[18:08] < MS-> But because he doesn't know how to parse them, the system is getting confused.

[18:08] < MS-> Which again, I can deal with now :-)

[18:11] < MS-> Mind you, now that I know that, I think I might sleep on it. I think I'm missing a very obvious trick here.

[18:12] < MS-> Also, when I do get this working, I'll eliminate the 100% CPU utilisation issue which it currently has, and then leave it running on kamaelia.org

[18:14] < Lawouach> k

[18:14] < Lawouach> cool

[18:15] < Lawouach> ping me tomorrow then

[18:22] < MS-> Cheers :-)

[19:54] *** dsoul has joined #kamaelia