News:

Pretty crazy that we're closer to 2030, than we are 2005. Where did the time go!

Main Menu

[java] Rolling (Shared) Queue

Started by Chavo, October 14, 2006, 02:52:09 PM

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

Print
Go Down Pages 1 2 All
User actions

Chavo

#15
October 21, 2006, 05:17:14 PM
That's what I am doing ;)

AntiVirus

#16
October 22, 2006, 02:06:02 AM
Eww.. go to hell! :D
The once grove of splendor,
Aforetime crowned by lilac and lily,
Lay now forevermore slender;
And all winds that liven
Silhouette a lone existence;
A leafless oak grasping at eternity.

"They say that I must learn to kill before I can feel safe, but I rather kill myself then turn into their slave."
- The Rasmus

Ender

#17
October 22, 2006, 09:20:18 PM Last Edit: October 22, 2006, 09:38:04 PM by Ender
Don't think of it as parallel processing. Think of it as ordered processing. When order matters, you think of it as ordered processing yet implement it so that it has the quirks and efficiency of parallel processing. There will have to be some thread control for ordered processing. Each connection object should have a static variable isBusySendingMessage or something. A boolean per packet in which order matters.

EDIT1:

Do you "pipeline" the messages such that while one message is being sent, another is being converted into a packet? (No time to look at the code.)

EDIT2:

Sorry if this post was unhelpful. I don't have time to look at the code, but thought I may go with the chance that this may help.

Chavo

#18
October 22, 2006, 11:34:13 PM
Quote from: Ender on October 22, 2006, 09:20:18 PM
Don't think of it as parallel processing. Think of it as ordered processing. When order matters, you think of it as ordered processing yet implement it so that it has the quirks and efficiency of parallel processing. There will have to be some thread control for ordered processing. Each connection object should have a static variable isBusySendingMessage or something. A boolean per packet in which order matters.
It does, the Queue's are on a different thread than QueueManager and all the relevant methods are synchronized.  Additionally there is a mandatory 500ms between processing new packets to ensure correct ordering with variable internet travel time.

QuoteDo you "pipeline" the messages such that while one message is being sent, another is being converted into a packet? (No time to look at the code.)
Packets are formed before they even get there, the only thing the PacketThread (encapsulates the socket) class has to do is retrieve the byte array.  And no they aren't pipelined even then.  I can explain in more detail, but its all in the code comments I think.

QuoteSorry if this post was unhelpful. I don't have time to look at the code, but thought I may go with the chance that this may help.
More helpful than no post, thanks :)
Print
Go Up Pages 1 2 All
User actions