Tcp Ip Video

[Aleshia Ducharme]

Higuys,

Im new with django and python and i have a question for you.

In my project i need a tcp/ip socket to listen for one client who is sending data. The client is already done and i cant change it.

My idea is to create a new thread and inside that tread open the socket but where can i instantiate this thread and socket? i need it in the runserver. Start all things at the same time.

Im new, so im using runserver because i followed the introduction tutorial.

So you are saying to create a separete server for the socket and logic right? but i cant acess django ORM in taht way right?

And it works like a charm! thank you very mutch! One last question, my socket will consume one thread in a while true loop, its better create a new thread for the socket? or django will manage that? And i can acess Django channels right?

I am still investigating but it seems that a SuSE update caused some troubles. In one environment all GWIA configuration files were gone (gwia.cfg, route.cfg, ...). Local admin was able to bring back all these files from a snapshot. At another location GWIA was not responsive. It seems that patching SuSE enabled postfix and its default main.cf which obviously troubled GWIA.

hi Andy Konecny any ideas or updates on this? Seeing something similar. GWIA is Running GW 18.4.1 140419 on SLES 15 SP1. Having issues with some hosts relaying to GWIA - but its intermittent...some messages go through and get processed, some don' t. When I check the logs for messages that don't get sent I see the tcp/ip read error

I ended up modifying the firewall on GWIA to allow all from these hosts, but still seeing the tcp/ip errors :( The sending servers have their firewall disabled for what it's worth... And I was mistaken they are on different vsphere clusters..

Most of those firewalls are simple port or IP binary decisions. It is the stateful inspection ones that look at (mess with) the application flow that cause most of these problems where the packets flow, but have issues.

Other big causes are switches having issues (failing or overloaded), or NIC driver issues causing some packet corruptions. I was sliding into the Xmas updating to see if that changed things at this client, since the mail is otherwise getting through. You are in a more urgent need of a fix. Perhaps running WireShark on the GWIA box to see if anything interesting pops out at the networking levels.

That is next in the queue for this issue at this client, though they do have bigger issues on the plate, so considering we aren't seeing mail not get through at all or noticing delays, that will be later. For Catia, likely a bigger need for the active dive in soon.

There is a lot of discussion about IP addresses etc for printer problems. There is no mention of a new feature for porting for printers, WSD port for plug and play of printers, I assume that IP addresses do not matter with WSD, My printer is confusingly set up for WSD port and TCP/IP port, can someone please expain

The WSD Port Monitor is a new printer port monitor in Windows Vista and Windows Server 2008. This port monitor supports printing to network devices that are designed to include Web Services for Devices (WSD) technology. Web Services for Devices allows network-connected IP-based devices to advertise their functionality and offer these services to clients by using the Web Services protocol. WSD-based devices and clients communicate over the network using a series of SOAP (Simple Object Access Protocol) messages over UDP and HTTP(S). WSD for Devices provides a network plug-and-play experience that is similar to installing a USB device. Web Services for Devices also defines a security profile that may be extended to provide additional protection and authentication using device-based certificates.

The WSD is not a port, but a port monitor. A port monitor looks at the information coming in from the TCP/IP port and makes changes or routing depending on what comes into the port.

When data comes into the TCP/IP port a port monitor is there watching for that to occur. The WSD port monitor would take over that function from the regular TCP/IP port monitor.

the point is: suppose I have a printer on the moon and the only things the printer has is power, paper and wireless tcp/ip port so NASA can sent it printing instructions, how then does wsd for devices help in this case!. does the printer device have to have a wsd server on it or what? is that simple!

To reply to your question re NASA and the Moon. WSD is not a printing port so you obviously need IP to print to it as WSD is not a network protocol or a network address - you have said this yourself in your own question - your printer has a wireless TCP port. WSD is a different type of port which allows secure communications and discovery over a network. WSD wouldn't make much difference on the Moon as NASA knows the name of the printer and its address, if they were trying to print to one of their NASA office printers here on earth then WSD would help as their Win7 PC's could discover the printing device and use it without having to tell all their users the printer name, which IP address it has been given or which server it is queued it is on.

You should respect the contirubters more on these forums. It's not their fault if you cannot grasp the difference on these technologies. WSD and IP are not the same thing so no comaprision can be made between them. Whether you can use them or not depends on which operating system you have on you client. Whether or not WSD is an advantage depends purely on the situation.

The explanation of what WSD does is excellent. My issue is why in the world would my I.P. printer port get replaced by "WSD..."? this has happen twice now and I'm not sure why. I have a Win 08 R2 print server.

So, you do them and the rest of us a disservice by responses of indignation "That was explained very well...It is not theposters fault you don't understand." is a unwarranted and inappropriate response.

While TCP/IP isuniversally usedfor network communications it is a hand shaking, reliable protocol SET and has the associated overhead and lower transfer due to the three way handshake and reliability function of the tcp transfer.

UDP on the other hand is a realtime/time critical protocol used when data packet loss is not as critical as in dns lookup and skype communications (this is why skype sometimes makes those annoying buzzy and dropped out missing parts). UDP sends the data packets in a stream, one after another and has no mechanism to resend missing or bad packets -the advantage of the tcp handshake and reliability...send packet,recieved packet, packet (missing/bad) resend request, transfer complete(end).

Most likely reason is that you have updated or installed the HP Universal Print Driver to run the pritners on your server. If you wanted to keep WDS off permenantly you would need to only use PS or PCL driver packages. WDS is more of a discovery / "advertise your presence"protocol. There is no harm is leaving it as WDS as it should be transparent to your operations or possibly benneficial to users if they have not been setup onto the printer by the IT staff or logon routine.

3a8082e126