|
Any buddy has some information about........
Good library for surface reconstruction from points cloud (points are with 3-dimension).
I have heard that "DELAUNY MESH TRIANGULATION 3D" can help in this kind of task.......
But i can't find good explanation for that algorithm.....
any one know about "DELAUNY MESH TRIANGULATION 3D" for C#.......
or any other algorithm for mesh triangulation or can say algorithm for surface reconstruction from points cloud in C#.....
One good Library COMPUTATIONAL GEOMETRY are available here...
But unfortunately it is in C++....
Thanks,
Regards
Pritesh Patel.
|
|
|
|
|
what is really wrong in this question...........
please give reason of down voting.
|
|
|
|
|
Probably because you didn't read but one or two of these[^].
|
|
|
|
|
I need a few very large ( >= 500K loc ) opensource C# and Java source code repositories to test some ideas. Do you know any?
Thanks,
|
|
|
|
|
|
Define "source code repositories".
|
|
|
|
|
|
Oh, 'cause mine's all spread around my hard drive.
|
|
|
|
|
Try looking at the larger projects on CodeProject, the Apache foundation or something like the Mono project. Make sure you ask the host first if you are going to be trawling their repository online, though.
|
|
|
|
|
Hello
I begin new project in C#. I have create "Client and Server" application. I want to sent any request to same user, but can't it . My question is, How can i it this and connection or request attribute must be "Ip Address" or "Domain name" or "Username".??.
Thanks in advance!
Regards,
Zaur Mammadli
|
|
|
|
|
please give more information about your question
what is your "Client and Server" application? socket application?
|
|
|
|
|
Hi,
For sending any request from one computer to another you have to use socket programming.
And according to the present problem you are facing you have to use IPAddress of the system to which you want to communicate
|
|
|
|
|
Need to transfer large data (Appox 1MB ). We are showing a chart in browser using jquery for that
we need to send point data (x amd y). want approx 1,00,000 point to send to client and showing there. size of these data is too large. so its not loaded in browser . when i use these same concept in 10000 points its working . i planned to compressed the data from sever and send back to client javascript is decompress the data and populate the chart. But is it possible to do. or have any specific compression algorithm is do for these.. or please share any other solution to these scenario...
WE are using the default browser is IE8
Thanks...
|
|
|
|
|
you have asked a similar question before and received an answer. Continue to use that thread, don't create new one.
How do you expect a user to see and use 100,000 point on a chart in the first place?
I know the language. I've read a book. - _Madmatt
|
|
|
|
|
Thanks for replay
Mark Nischalke wrote: How do you expect a user to see and use 100,000 point on a chart in the first place?
User can view the report. After generating the report chart points based on the performance.
it will send back to browser. so threading is not feasible one because otherwise every request we generate a points. want to send back entire value at once.
|
|
|
|
|
I missed the previous thread..
Can you give more information about the data? A sample data set would also help enormously. I hope it's not floating point coordinates - the techniques necessary to compress that are quite complicated.
Is 1MB really too big, though? It doesn't sound so big to me..
|
|
|
|
|
Don't send a million points, or even 10,000. A graph will be at most 500 pixels across, so if it's timeseries type data (only one Y value per X) then you need at most 500 points. Filter the points that get sent back so there are enough to view a nice graph, and don't send everything.
The TCP stream should already be compressed with modern hosts and browsers. But sending a megabyte in response to an AJAX call is not good netiquette anyway.
|
|
|
|
|
hi
is it be better to open connection to database -
make any querys...update....delete -
and after i use to close this connection
or
open the connection when the program load -
and close when the program close ?
thanks in advance
|
|
|
|
|
this gets asked at least once a week around here.
the answer was and still is: open-use-close at the functional level (i.e. within a single method), not at the application level.
database connection licenses are expensive so you shouldn't have them sit idle, and connection pooling will reduce the technical cost of opening and closing connections.
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.
|
|
|
|
|
Luc Pattyn wrote: database connection licenses are expensive so you shouldn't have them sit idle
Depends quite a lot on the licensing model
|
|
|
|
|
Right. But then, the licensing model can always change, so better be safe than sorry.
And if expensive things aren't allowed to sit idle anymore, we would have problems with managers, bankers, politicians, and more.
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.
|
|
|
|
|
|
Don't be expensive. Close the connection when ever your process is over!!
|
|
|
|
|
MOST of the time (but certainly not all of the time), close your connection between database calls. If you're going to make several subsequent calls one after the other, close it after the last one.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
This depends on the application. If you have simple database tasks, closing and reopening is fine. But if you have several calls to the database in a single unit of work and you need (as you should need) transactions, you must keep the connection open at least to the end of the transaction.
Another point is that if you use notification mechanisms from database to the client, you'll need an open connection in order to receive notifications.
|
|
|
|