Till Backhaus
2006-08-12 12:13:12 UTC
hello again,
when i contributed the no-brs patch in june i was told
and proposed the reassembling of gpg-messages that
have been sliced into pieces someone told me about
the MIS_HANDLE_MESSAGE_FRAGMENTS - stub in the fire 2.0 tree.
Unfortunately i lost that message.
Now, as some month went by and nothing happened to that stub
i am willing to provide that part.
Since my knowledge about the architecture of fire is poor i
suggest to discuss that feature first.
maybe the following questions will help to start discussion:
1. Which fragments (apart from sliced gpg-messages) should be
joined?
2. Should message delivery be delayed some amount of time to allow
other messages to arrive? I'm talking about 0.3 seconds here.
3. How should one keep track of message parts?
cheers
Till Backhaus
when i contributed the no-brs patch in june i was told
and proposed the reassembling of gpg-messages that
have been sliced into pieces someone told me about
the MIS_HANDLE_MESSAGE_FRAGMENTS - stub in the fire 2.0 tree.
Unfortunately i lost that message.
Now, as some month went by and nothing happened to that stub
i am willing to provide that part.
Since my knowledge about the architecture of fire is poor i
suggest to discuss that feature first.
maybe the following questions will help to start discussion:
1. Which fragments (apart from sliced gpg-messages) should be
joined?
2. Should message delivery be delayed some amount of time to allow
other messages to arrive? I'm talking about 0.3 seconds here.
3. How should one keep track of message parts?
cheers
Till Backhaus