KRISHNENDU MUKHERJEE wrote: RAVI TCP IS USED BY WEBSERVICES FOR COMMUNICATION PURPOSES.WE CAN USE TCP(TRANSMISSION CONTROL PROTOCOL)OR UDP(USER DATAGRAM PROTOCOL). Actually no. It can operate on any protocol that can send text over a pipeline. http, ftp, and a few others. KRISHNENDU MUKHERJEE wrote: 1.Application layer:through which you are interacting while surfing. This is used to dissembling packets, not the web KRISHNENDU MUKHERJEE wrote: 2.Presentation Layer:it is required for data encryption,data compression,data representation in excel,doc etc format. This is what you see on an application or the web. KRISHNENDU MUKHERJEE wrote: TCP-header.Here we need TCP protocol. And actually TCP is only need if you have to have an acknowledment of the transmission. For instance, online video games dont need to waste extra resource seeing that you get data every second. So they send UDP packets, which are one way. Hope this clears some misconceptions 1 line of code equals many bugs. So don't write any!!

Isn't "internet-optimizer" some sort of spyware/virus/toolbar thingy? --------------------------- 127.0.0.1 - Sweet 127.0.0.1

hi there, take a look on this article: Tracing] << >>

Microsoft is pushing System Diagnostics logging, but I think you can argue for and against both methods. There are two clear cut cases: 1) Windows Services should definitely use "System" logs. 2) If you still have to support Win98, there are no system logs, so a conventional file method is your only option. Of course you could create multiple versions, but I see no compelling reason to do so just for logging. There are pluses and minus for both. For example, if you need to troubleshoot a weird problem it is a lot simpler to ask a client to find a folder and e-mail you a log file than it is to try to explain to them how to save a System log to a file and send it. On the other hand if you actually have access to the Event log viewer, you can assign levels when you write messages and then System logs make it easy to find critical errors out of possibly a large number of insignificent messages. Personally, I use both methods. If it is an application that I will be managing directly on a server I have access to I will use a System log. If it is a "3rd party app" that I don't expect to have direct access to once I've released it I ten d to still use the old fashioned flat file approach for the reason I've mentioned - I can always request an error log by e-mail if a problem arises. You really have to evaluate your own specific situation.

Hi there, As you already know that the EventLog[^] class allows you to write information to the window event log, so you can use it in your application for logging. However, using only the event log for logging in an application should not be flexible as your clients sometimes might want your application to log in a text file, or a datastore... other than the event log. So it is better to use a library like the log4net[^] or the Logging Application Block[^] in the Enterprise Lib for logging as they provide many more options.

Yeggu, Whilst transitioning the application to Production environment, you may like to ensure that the application is compiled in 'Release' mode against the default 'Debug' mode. This way, your application size would be significantly less, since no debug symbols would be included. Also, in the web.config, you can set the debug mode to false. Did this attend to your query? Vasudevan Deepak Kumar Personal Web: http://www.lavanyadeepak.tk/ I Blog At: http://deepak.blogdrive.com/

Thank u very much Leena. The problem was solved. Thanku, yeggu