Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » U++ Library support » U++ MT-multithreading and servers » SlaveProcess should be moved from Web to Core
SlaveProcess should be moved from Web to Core [message #2145] Sun, 02 April 2006 13:25 Go to next message
hojtsy is currently offline  hojtsy
Messages: 241
Registered: January 2006
Location: Budapest, Hungary
Experienced Member
There is a SlaveProcess class in Web package. I think this functionality is not connected to Web, and should rather be where the Thread functionality is: in the Core package.
Re: SlaveProcess should be moved from Web to Core [message #2158 is a reply to message #2145] Sun, 02 April 2006 15:57 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 13975
Registered: November 2005
Ultimate Member
hojtsy wrote on Sun, 02 April 2006 07:25

There is a SlaveProcess class in Web package. I think this functionality is not connected to Web, and should rather be where the Thread functionality is: in the Core package.


I more or less agree (as does Tom who recuctantly put it to the Web), however the trouble is that SlaveProcess derivate uses Socket which still is in the Web...

Mirek
Re: SlaveProcess should be moved from Web to Core [message #2159 is a reply to message #2158] Sun, 02 April 2006 16:14 Go to previous messageGo to next message
fudadmin is currently offline  fudadmin
Messages: 1321
Registered: November 2005
Location: Kaunas, Lithuania
Ultimate Contributor
Administrator
luzr wrote on Sun, 02 April 2006 14:57

hojtsy wrote on Sun, 02 April 2006 07:25

There is a SlaveProcess class in Web package. I think this functionality is not connected to Web, and should rather be where the Thread functionality is: in the Core package.


I more or less agree (as does Tom who recuctantly put it to the Web), however the trouble is that SlaveProcess derivate uses Socket which still is in the Web...

Mirek



To move both or a separate package?
Re: SlaveProcess should be moved from Web to Core [message #2160 is a reply to message #2158] Sun, 02 April 2006 16:15 Go to previous messageGo to next message
hojtsy is currently offline  hojtsy
Messages: 241
Registered: January 2006
Location: Budapest, Hungary
Experienced Member
You mean the RemoteSlaveProcess? That could stay in Web. I think it is normal for a non-Core class to derive from a Core class. Still the LocalSlaveProcess should be usable withouth the Web package.
Re: SlaveProcess should be moved from Web to Core [message #2162 is a reply to message #2160] Sun, 02 April 2006 17:54 Go to previous message
mirek is currently offline  mirek
Messages: 13975
Registered: November 2005
Ultimate Member
hojtsy wrote on Sun, 02 April 2006 10:15

You mean the RemoteSlaveProcess? That could stay in Web. I think it is normal for a non-Core class to derive from a Core class. Still the LocalSlaveProcess should be usable withouth the Web package.


Well, I have that on ToDo for quite some time.

There definitely will be a huge codequake soon: T* packages will be removed from uppsrc (while move some worthy packages to Core/CtrlLib), Socket and *SlaveProcess will be moved to Core, PCRE package added etc...

Mirek
Previous Topic: Core multithread dangers
Next Topic: Web/TServ [BUG][FIXED]
Goto Forum:
  


Current Time: Fri Apr 19 04:12:26 CEST 2024

Total time taken to generate the page: 0.06199 seconds