EldoS | Feel safer!

Software components for data protection, secure storage and transfer

Multiple Threads

Also by EldoS: Solid File System
A virtual file system that offers a feature-rich storage for application documents and data with built-in compression and encryption.
Posted: 01/29/2010 10:16:43
by Malcolm Toon (Standard support level)
Joined: 01/20/2010
Posts: 22

A quick question about threads... is there any way to have dedicated threads for specific messages? If I have certain messages that are atomic and don't require being queued or processed sequentially, but I want them to come in on the same sockets, how could I do this?

Thank you!
Posted: 01/29/2010 11:21:43
by Eugene Mayevski (Team)

No, you should have a dedicated messenger and transport for them.

Sincerely yours
Eugene Mayevski
Posted: 01/29/2010 12:02:59
by Malcolm Toon (Standard support level)
Joined: 01/20/2010
Posts: 22

Ah, ok. Does that mean I could spin up multiple threads with individual instances of the messaging system?
For Example:
Thread 1: Socks Port: 1001; Queue1; MsgID: 1 (and it's own messenger component)
Thread 2: Socks Port: 1002; Queue2; MsgID: 2 (and it's own messenger component)

Have you ever built a scenario like this? MC has been working fantastically for our uses, but I'm trying to tweek out all the CPU power I can (one thread per core for example).

Thank you again for all the great help!
Posted: 02/02/2010 10:51:15
by Eugene Mayevski (Team)

Yes, you can do the described.
Note, that
(a) SOCKS is a proxy server type. Don't confuse SOCKS with sockets.
(b) SocketTransports spawns at least two helper threads (one for listening and a thread per each socket connection, incoming or outgoing).

Sincerely yours
Eugene Mayevski



Topic viewed 4024 times

Number of guests: 2, registered members: 0, in total hidden: 0


Back to top

As of July 15, 2016 EldoS business operates as a division of /n software, inc. For more information, please read the announcement.

Got it!