Hi guys i am using windows server 2008, i set up a domain, and several clients joined.
I am trying to implement a socket server by using epoll.
I have currently created a simple tcp socket client application that sends and receives messages from a dotnet server application I have created. The application itself actually works however there are a few things I would like to know if they are possible or not.
I'm working on a website, and I need to test the functionality of sending email messages from ASP.NET, something like this:
Dim msg As New MailMessage("email1", "email2")
msg.Subject = "Subject"
msg.IsBodyHtml = True
msg.Body = "Click here."
Dim client As SmtpClient = New SmtpClient()
client.Host = "My-Server"
client.Port = 25
client.DeliveryMethod = SmtpDeliveryMethod.Network
client.Send(msg)
I am developing an application in which client sends messages to server and server receives messages. But in my application when I am sending message, it is received by server only once. If I have to send message again to server I have to Force close the application and then again send message. Means in continuous manner I have to send data to server. Below is my code.
It's a server which listens at https://. It uses a self-signed cert. So, each time when I access it, I will be prompted to trust this untrusted site. However, I always get the following error in the server log.
I'm writing a simple chat client in C++ on linux to connect to a win32 chat server on my computer also written in C++. I'm confident that the server works but the chat client is giving me some trouble. I'm forking the chat client and have one process dealing with incoming messages and another dealing with sending messages.
Hello all
I'm really hoping someone can help me with a strange problem I'm experiencing under Ubuntu Server 10.04 LTS.
I have a server application listening for TCP/IP connections. When it receives a connection, sometimes all works as expected and sometimes not. In the cases where things do not go well, the server reports the socket is open and connected, but receives no data.
Example: If a client wants to talk to a server, it just tells the server that it wants to establish a connection, then the server confirms. People say that the third step's there so as to let the server knows it can sends data to the client successfully. However, I think the server can implement something like time-out. If the client takes too long to respond, the server can go ahead to:
1.