Catalog group code data - is it Master data or Configuration data

Question

Hi all,
Need some clarifications between Master Data and Configuration data. In CRM we use catalog code groups and codes for ticketing systems. The code groups and codes are defined in SPRO (IMG) once and consumed in catalog schema’s at client level. I refer to  this code groups and codes in SPRO as Master Data, cause it is shared across modules and does not change so frequently. However I was recently corrected by my manger that since it is transportable it cannot be Master Data, it is configuration data. And tasked to contact SAP and get the correct/official answer. Is it configuration data or master data and what is the determination.
BTW, allow me to clarify that we like to know the right answer for proper documentation and this is not the who’s right challenge J
Best,
Michael Sh

Answer 1

1.server creates new client thread for each newly accepted connection Good. Make sure the server doesn't do any I/O in the accepting thread, including even construction of input and output streams.
2.if one of these client threads receives some data from the client, then:
3. this client thread creates new ControlThread object (and passes received data to it )Why? What does the Control thread do that the client thread can't do? Does the client thread really create a new Control thread per piece of received data? What's the purpose of the Control thread here?
4. ControlThread object in turn spawns a new thread Again why?
From your description you appear to be creating:
(a) a thread per connection
(b) a thread per piece of received data
(c) another thread per (b)
What you probably need for a chat server is an input thread and an output thread per connection. The output thread should read a queue and the input thread should write to the appropriate queue(s), making sure you don't create a loop by sending the client's own data back to him.
5. Finally, this spawned thread will send data to all client apps.No. Use one output thread per connection, as described above. As writing to a socket can block, you shouldn't use a single thread for writes to more than one client, otherwise the whole system can stall due to one non-co-operating client.
a) how scalable is this server app?It's about as non-scalable as it could possibly be. You will have an explosion of threads per item of data received if you've described it correctly, and you already have too many threads per connection.
b) what would you�ve done differently ( in terms of basic program structure )?Almost everything: see above.
Perhaps creating ControlThread object each time data needs to be sent to other client apps is a bad ideaMost definitely.