|
I see, the OP modified the post. 
Yusuf
Oh didn't you notice, analogous to square roots, they recently introduced rectangular, circular, and diamond roots to determine the size of the corresponding shapes when given the area. Luc Pattyn[^]
|
|
|
|
|
ha ha ha 
|
|
|
|
|
I don't think ASP.NET is the right was to write a chat app, personally, although google chat is OK, MSN is much better for a variety of reasons, most of which have to do with it not being a web app.
Christian Graus
Driven to the arms of OSX by Vista.
"I am new to programming world. I have been learning c# for about past four weeks. I am quite acquainted with the fundamentals of c#. Now I have to work on a project which converts given flat files to XML using the XML serialization method" - SK64 ( but the forums have stuff like this posted every day )
|
|
|
|
|
there are more chat applications available in google...
and.. if u want u can create your own chat control..with application variable...
i m using my own chat application in my asp.net application.
http://cutesoft.net/asp.net+chat/Default.aspx
this is one version...from CUTE soft
Regards
Rajeesh MP
|
|
|
|
|
Hi Rajesh, while posting in forum please make sure to whom you are replying. In this thread you have replied to CG message, but I believe you should reply it to the original tread rather than CG. Your post may help to the 'dotnetmember', but not CG  . So this is my suggestion to you, that while posting make sure you are replying to the right post.
cheers,
Abhijit
CodeProject MVP
|
|
|
|
|
thank you Abhijith..
now i checked yesterday posts....i did same like this for u also...sorry
Regards
Rajeesh MP
|
|
|
|
|
|
(I'm from germany but I try my best speaking english)
Hello everybody,
We are currently developing a webpage where people can upload pictures. Therefor we created an asp.net webservice to be able to upload pictures from various clients and operating systems via soap. This webservice has an "upload(byte[] b)" method. I'm currently working on a C# client. When uploading small files with a size of about 5kb, everything works perfect, but when I try to upload pictures in full size (which is 800x600 at about 40kb) upload sometimes fails due to timeout, although I set the time to 60 seconds, which is definitly enough. The maxRequestLength and requestLengthDiskThreshold are big enough. I wonder if there's another limitation which I have to edit (web.config, IIS, firewall) or if the problem is something different.
The webservice runs on win 2003 server and the client on win xp
Thanks in advance
|
|
|
|
|
circle-driver wrote: although I set the time to 60 seconds,
Where did you set your timeout?
Look Here[^] and here[^] ( see the timeouts section )
Yusuf
Oh didn't you notice, analogous to square roots, they recently introduced rectangular, circular, and diamond roots to determine the size of the corresponding shapes when given the area. Luc Pattyn[^]
|
|
|
|
|
<pre><system.web>
<httpruntime executiontimeout="12136" maxrequestlength="12204" requestlengthdiskthreshold="12512" /></system.web></pre>
if u r increasing this values in web config....your session will not timeout
Regards
Rajeesh MP
modified on Thursday, April 9, 2009 1:05 AM
|
|
|
|
|
How do you know it does not time out? I don't know how the request is handled inside of the framework, but when we were making a java client and writing the soap-handler-class on our own with sockets and streams, the requests timed out, because we did some miscalculation on "Content-Length" and the Server waited for more, thus a bigger waiting-time wouldn't help.
Nevertheless I will give it a try and use extreme large values to make sure it doesn't help (No offence!).
|
|
|
|
|
Client:
UploadService.Service myService = new UploadService.Service();
myService.Timeout = 60000; Webservice(web.config):
<httpRuntime maxRequestLength="2048" executionTimeout="120" requestLengthDiskThreshold="tried different numbers" /> Since some pictures upload within a few seconds and others timeout after 60 seconds although they only have a slightly different size I guess there has to be another reason.
To make sure I give you all information you might need, here's how I created the proxy class in case it's important.
Wsdl /language:cs /protocol:soap /namespace:UploadService /out:UploadService.cs http:
|
|
|
|
|
maxRequestLength=".........." executionTimeout="....."
you give a big number
|
|
|
|
|
Meanwhile I found the problem and fixed it. Since I'm sitting on an ubuntu computer and use VirtualBox to emulate Windows for .net development the problem where the network settings of the virtual machine.
Thanks for your help.
|
|
|
|
|
cool 
Yusuf
Oh didn't you notice, analogous to square roots, they recently introduced rectangular, circular, and diamond roots to determine the size of the corresponding shapes when given the area. Luc Pattyn[^]
|
|
|
|
|
I have new interesting and weird information for you. Most of the bytes uploaded reach the Server and when the request times out or if I kill the client after some seconds (no difference) the bytes get written into the file and the picture looks like crap in the lower part. I tried it three times with the same pic which has 113919 bytes. On server side I once counted 113094 and twice 113318 bytes. For some reason those last bytes don't reach the server. I now hope wsdl.exe gave me a corrupt file, and I will create a new one. Since I don't really believe in that, more suggestions are welcome.
Edit:
I tried not using wsdl.exe and create a web reference in visual studio instead. Same problem like before.
Edit2:
I guess we are making process  . Well, not really. After I found the following blog entry while searching the web for "asp.net webservice packet loss" I really thought that's it. But after I finished reading, I realized that there's no solution given at all. I started wireshark and I found these "tcp/ip retransmissions" as well, but still I have no clue what that's all about. By the way, I meanwhile moved to another server (new provider, more ram and cpu, fresh install) and nothing changed.
modified on Thursday, April 9, 2009 6:41 PM
|
|
|
|
|
Hello, I'm relatively new to c# and even newer to asp.net and ado.net.
I'm trying to improve my skills in the asp.net and ado.net areas.
I'm working on an a sample app where I want to display items in a web page based on what the user has selected from a drop-down list.
A couple of questions I have while on this learning path:
1 -Are all database queries and "presentation" done within the .aspx files, or are some done in the .cs files?
Thanks in advance.
---------
Jeff
|
|
|
|
|
Good question. In fact, your database queries SHOULD come from a seperate dll which encapsulates DB code. Microsoft have added ways to do database stuff in the ASPX, but no-one uses them except hobbyists and people who don't know/don't care about writing good code. You should run from any control that has you typing SQL into your aspx. You should try to wrap your database code into a seperate layer. Ideally, your database layer would not return database objects but take and return lists of classes in your project.
Christian Graus
Driven to the arms of OSX by Vista.
"I am new to programming world. I have been learning c# for about past four weeks. I am quite acquainted with the fundamentals of c#. Now I have to work on a project which converts given flat files to XML using the XML serialization method" - SK64 ( but the forums have stuff like this posted every day )
|
|
|
|
|
Jeff,
I like to break my design into three layers
1. Presentation
2. Business Logic
3. Database
1. In presentation layer I put only those that are of UI related. This will go directly into the aspx pages, user controls (usually I create on separate dll) and any UI related logic
2. Database. This is strictly database related classes. NO other code belongs here.
3. In business logic goes any middle-ware code that does not belong to any of the two categories.
Now, notice how I said 'This goes to separate dll' in the first case. I don't go crazy in creating many dlls. The rule of thumb I use is, if the code can be reused somewhere else, then I create it in its logical dll, so I can easily take it to another project and reused. That means the other layers may have multiple dlls as well.
Again, there are projects I have worked which they have only 2 layer or more than 3 layers. It does not have to be only 3 layers. The scope of the project will decide how you want to break your logical designs. In some cases you may be able to get away with single layer.
Yusuf
Oh didn't you notice, analogous to square roots, they recently introduced rectangular, circular, and diamond roots to determine the size of the corresponding shapes when given the area. Luc Pattyn[^]
|
|
|
|
|
Christian, Yusuf, thanks for your timely and informative replies. I have 2 simple (hopefully) questions that come to mind based on your responses:
- You are both saying create separate .dlls. You do NOT mean the .cs files that are created in Visual Studio when you create a .aspx page, correct?
- I've been through a couple of "introductory" books on c# and they all seem to show the database access code occurring in the .aspx file. That figures if they're just trying to show you enough to get started. I'll poke around in codeproject a lot more but: what would be the best way you all recommend to learn to create web sites the right way, using .dlls?
Thanks again for your informative replies!
--
Jeff
|
|
|
|
|
jboyd111 wrote: You are both saying create separate .dlls. You do NOT mean the .cs files that are created in Visual Studio when you create a .aspx page, correct?
- The .cs files modularize your code. In most cases If the class is big enough I put it in one .cs files, but if the class is small, then I combine logical classes together.
- A dll is an assembly (or library) that contains certain functionality, for example Database layer
Most books in programming jump into the topic in discussion they throw everything in one place. The idea is to teach the language not necessarily the design. So, take it with grain of salt.
Here [^] are CP articles on design and strategy, should you need assistance don't hesitate to post your question in appropriate forum
Yusuf
Oh didn't you notice, analogous to square roots, they recently introduced rectangular, circular, and diamond roots to determine the size of the corresponding shapes when given the area. Luc Pattyn[^]
|
|
|
|
|
Thanks Yusuf. I knew what dlls vs source (.cs) files were, I just hadn't seen .dlls used in any of the web (.aspx) examples I came across. I'm still trying to find where the actual compiled code from my web projects go, but that's another thread.
Thanks for the pointer to the Design and Architecture articles and info. That should keep me busy for awhile
--------
Jeff
|
|
|
|
|
jboyd111 wrote: I'm still trying to find where the actual compiled code from my web projects go, but that's another thread.
Good question: In the case of dll you know where that goes.
In the case of asp.net, the compiled code gets copied into framework temp folder which is located in %WinDir%\Microsoft.Net\Framework\%version%\Temporary ASP.NET Files\%ProjectName%
where
%windir% = windows directory (by default in XP c:\windows)
%version% = Framework version (for example v2.0.50727)
%projectname% = asp.net project
Yusuf
Oh didn't you notice, analogous to square roots, they recently introduced rectangular, circular, and diamond roots to determine the size of the corresponding shapes when given the area. Luc Pattyn[^]
|
|
|
|
|
Yusuf, my friend, you are my new hero! Thanks for taking the time to answer such rudimentary questions from a "newbie" such as myself.
---
Jeff
|
|
|
|
|
It was real pleasure helping people like you. Feel free to post any further question you may have in appropriate forum.
Good luck learning asp.net
Yusuf
Oh didn't you notice, analogous to square roots, they recently introduced rectangular, circular, and diamond roots to determine the size of the corresponding shapes when given the area. Luc Pattyn[^]
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
