|
immer ist alles dringend!
I cannot remember: What did I before google?
|
|
|
|
|
Thomas Krojer wrote: immer ist alles dringend!(everything is always urgent)
You are right. And CP becomes their emergency room.
Ignorance of the ability brings disability.
|
|
|
|
|
hi.
i need codes in c# for recording video with webcam.
this program have 3 buttons
1.turn on webcam
2.record
3.save the recordes
|
|
|
|
|
A little effort via Google and you will find them. You may also like to check this[^] out, especially point 2.
The best things in life are not things.
|
|
|
|
|
naalgo wrote: i need codes in c# for recording video with webcam.
I'll build it for $5000.
I are Troll
|
|
|
|
|
I'll build it for $4999, but I won't do as good a job as Eddy
|
|
|
|
|
5000? 11900! You offerd it to cheap!!
I cannot remember: What did I before google?
|
|
|
|
|
Thomas Krojer wrote: 5000? 11900! You offerd it to cheap!!
I tried to undercut all other offerings, but as you can see it didn't work
I are Troll
|
|
|
|
|
Here are some codes you may find useful:
using System;
using System.Collections.Generic;
The rest I leave as an assignment for you.
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
|
|
|
|
|
|
You could always buy a webcam, install the software that goes with it, finds the appropriate dll's, reverse engineer them, re-format them to your coding standards, framework and language and then compile.
V.
|
|
|
|
|
Somewhere, a polar bear just died because you wasted electricity typing that.
|
|
|
|
|
Hello Everybody,
I have a component which is not serialize and now i am trying to save it in file with the use of binary serialization.
But it's not saving yet. And shows the message your component is not serialize.
So please help me to serialize this object.
If you can think then I Can.
|
|
|
|
|
It's all explained here[^] in this CodeProject article.
The best things in life are not things.
|
|
|
|
|
Short answer: put [Serializable] on the component and make sure that all its fields are themselves serialisable.
|
|
|
|
|
Dear Sir,
Thanks for reply. But this component is not develop by me. this is third party control.
So how can i do that?
Thanks Again
If you can think then I Can.
|
|
|
|
|
Then, if the control does not support serialisation by some easy mechanism (either having [Serializable], implementing ISerializable or providing something like ReadXml/WriteXml methods), you will have to write a wrapper class to serialise all the properties that you can get hold of.
|
|
|
|
|
Hi Can Any One Guide Me How To Encrypt/Redirect The Whole Url In The Address Bar.
Help Me
|
|
|
|
|
You can't encrypt the whole URL. How would the web request know what the endpoint was?
|
|
|
|
|
Hi.
I have a chat site (http://www.pitput.com) that connects user via socket connections.
I have in the client side a flash object that opens a connection to a port in my server.
In the server i have a service that is listening to that port in an async matter.
All is working fine except when i talk to someone after an unknown period of time(about couple of minutes) the server is closing my connection and i get an error in the server :
" A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond".
I dont know how exactly the tcp socket works. does it checking for "live" connection every couple of seconds? how does it decide when to close the connection? Im pretty sure that the close operation is not coming from the client side.
Thanks.
|
|
|
|
|
Wireshark is your friend. Get it started, do your thing, and when you get the error, stop Wireshark and look through the trace. It's probably worth saving the trace then applying an IP filter to see only the traffic of interest. You will be able to see which end failed to respond (and, importantly, the packet that did not get a response).
Cheers,
Peter
Software rusts. Simon Stephenson, ca 1994.
|
|
|
|
|
Haim Nachum wrote: I dont know how exactly the tcp socket works. does it checking for "live"
connection every couple of seconds?
No.
Haim Nachum wrote: how does it decide when to close the connection? Im pretty sure that the close
operation is not coming from the client side.
The connection is not not closed. You are getting a timeout failure.
Haim Nachum wrote: and i get an error in the server :
You get that error in the server? I would expect that from a client. Clients connect to servers not the other way around.
|
|
|
|
|
TCP operates a timeout if no packets are sent for some time, because this is usually a sign that the connection has been lost. The time varies but is usually around 30s to a couple of minutes. If you want to maintain a connection despite no user interaction, you need to send 'keep-alive' packets or 'pings' every few seconds (one every 20s should be enough) to keep the connection open. However, remember that if you do this, idle connections will never time out and you can run out of server sockets if too many people leave your app open, so you then should have some client code that logs out and closes the socket after a longer inactive time (30 mins or so).
|
|
|
|
|
BobJanova wrote: TCP operates a timeout if no packets are sent for some time, because this is
usually a sign that the connection has been lost.
TCP does not do that.
BobJanova wrote: you want to maintain a connection despite no user interaction, you need to send
'keep-alive' packets or 'pings' every few seconds (one every 20s should be
enough) to keep the connection open
You do that because the server or firewall requires it - not TCP.
BobJanova wrote: However, remember that if you do this, idle connections will never time
out and you can run out of server sockets if too many people leave your app
open, so you then should have some client code that logs out and closes the
socket after a longer inactive time (30 mins or so).
That of course is an architecture problem. If you server is going to respect keep-alives then it must exist in an enterprise that doesn't expect an unlimited number of client all with persistent connections.
One alternative to that possibility is to close even connections that are in use after a given time period. Or require a connect/message/close protocol like http.
|
|
|
|
|
TCP does not do that.
I thought I'd read that, but if it is not TCP, then it is the operating system, because if you open a TCP connection to your own server and send nothing in either direction, at some point it will get closed.
|
|
|
|