egghelp/eggheads community

socket info

2005-03-08T04:35:46-04:00

never mind i found out server socket waits untill one thread is done then moves on to the next one..

Statistics: Posted by Ofloo — Tue Mar 08, 2005 4:35 am

socket info

2005-03-07T14:19:25-04:00

no and no

it won't create a new interpreter

it won't overwrite other connection's data

quoting from [socket] manpage:

Server sockets depend on the Tcl event mechanism to find out when new connections are opened. If the application doesn't enter the event loop, for example by invoking the vwait command or calling the C procedure Tcl_DoOneEvent, then no connections will be accepted.

I'm unsure what exactly your problem is; maybe you need to clarify

If you just need to get a TCL server app to work, check out TCL's wiki for simple examples

Statistics: Posted by demond — Mon Mar 07, 2005 2:19 pm

socket info

2005-03-06T20:58:23-04:00

TCL doesn't implement threads - but you can emulate threads using multiple interpeters; there is however the Thread extension which allows you to experience the wonderful pitfalls of multithreaded programming

I highly doubt you need threads to drive your purely event-driven I/O tasks

just as i expected but i can't say that answers my question.. does socket -server open a new interpreter each time yes or no ? also i sad "like" threads never sad it used em, if it uses multiple sessions i know it would open tclsh just an other time .. thing is does it yes or no ..

so basicly does server socket open a new interpreter which i highly doubt

it also can open a new interpreter without making a new scope like this it could make one scope and multiple threads..

Code:

socket -server server 6666proc server {s i p} {  global somevar}

for example if the above is the case and 2 connections are made at once will somevar overwrite the data in the other connection ? or will it delay it and finish one at the time ..

Statistics: Posted by Ofloo — Sun Mar 06, 2005 8:58 pm

socket info

2005-03-06T17:37:35-04:00

TCL doesn't implement threads - but you can emulate threads using multiple interpeters; there is however the Thread extension which allows you to experience the wonderful pitfalls of multithreaded programming

I highly doubt you need threads to drive your purely event-driven I/O tasks

Statistics: Posted by demond — Sun Mar 06, 2005 5:37 pm

socket info

2005-03-06T15:39:39-04:00

I guess the only way to find out is to use it for a while.
Variable arrays based on -socketname (if used) may help.
Hard to give advice with not enough info for me to work with.

its not me whom is gone use it so i might find out only months later.. couldn't hurt to ask tho ..

Statistics: Posted by Ofloo — Sun Mar 06, 2005 3:39 pm

socket info

2005-03-06T14:07:22-04:00

I guess the only way to find out is to use it for a while.
Variable arrays based on -socketname (if used) may help.
Hard to give advice with not enough info for me to work with.

Statistics: Posted by DragnLord — Sun Mar 06, 2005 2:07 pm

socket info

2005-03-06T13:53:00-04:00

hmm its kinda big it works its finished just don't wana come before suprises later on.. more then one file..

Statistics: Posted by Ofloo — Sun Mar 06, 2005 1:53 pm

socket info

2005-03-06T13:45:36-04:00

I misunderstood what your aim was.
Can you post some of the code you want to use?
Might help to understand it a little better.

Statistics: Posted by DragnLord — Sun Mar 06, 2005 1:45 pm

socket info

2005-03-06T09:40:30-04:00

according to the TCL doc, it does.
For each connection Tcl will create a new channel that may be used to communicate with the client.
but probably these functions itself cannot run at the same time, they will run one after another. but that should be no problem. when you use non-blocking I/O.

my question is if there will be a new scope for each connection like threads with a parrent its actualy for my webserver in tcl i am asking i can't find the thread on the forum but i once asked how to do code evaluation there did user suggested to use namespaces and a global return variable problem is if sessions do overwrite each other then i can't use global variables like that (not the command global but variable, just saying global variable cause i mean its not local inside the proc)

using the -async switch usually yields the best results with sockets
if you find a better way, please let us know

-async is not supported by servers

Statistics: Posted by Ofloo — Sun Mar 06, 2005 9:40 am

socket info

2005-03-06T03:46:14-04:00

no i am asking for global variables so they don't overwrite eachother..

there are no global default variables using [socket -server ], or are you asking something else?
if you are going to save the sock# like $::sock you will of course encounter an overwrite of the variable, but luckly you won't need to save it outside the interacting proc, because the proc will be called with the sock# as argument, maybe you should really read The Manual?!

Statistics: Posted by De Kus — Sun Mar 06, 2005 3:46 am

socket info

2005-03-06T02:08:16-04:00

using the -async switch usually yields the best results with sockets
if you find a better way, please let us know

Statistics: Posted by DragnLord — Sun Mar 06, 2005 2:08 am

socket info

2005-03-05T22:05:36-04:00

no i am asking for global variables so they don't overwrite eachother..

Statistics: Posted by Ofloo — Sat Mar 05, 2005 10:05 pm

socket info

2005-03-05T19:57:42-04:00

according to the TCL doc, it does.

For each connection Tcl will create a new channel that may be used to communicate with the client.

but probably these functions itself cannot run at the same time, they will run one after another. but that should be no problem. when you use non-blocking I/O.

Statistics: Posted by De Kus — Sat Mar 05, 2005 7:57 pm

socket info

2005-03-05T14:54:31-04:00

is a server socket in tcl multi threaded under an eggdrop yes or no..

can there be 2 sessions at once ..?

Statistics: Posted by Ofloo — Sat Mar 05, 2005 2:54 pm