Re: How complex is this, really?


"sam" <scarleton@xxxxxxxxx> wrote in message
news:6a39d281-18a9-4fa9-b68a-81fb13006608@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

There is one day the product is delivered by all the scouts to all the
customers. There is someone at a central location that is able to
take calls when customers call and complain they did not get the
correct items. In the past they had to figure out which order number
the person was, find the paper order to determine of there was an
error in entering the order or if the customer marked the wrong thing.

ah, this one is easy ... outsource the call center to India, put people on
hold for 45 minutes and then drop the call ... it works great for Dell;
they save money and I live with the problem


I am really very open to any approach that is fast and easy. Can you
give me a bit more detail on HttpWebRequest? I looked it up and it
looks like a generic way to post data to a web server.

it's a way to make a request over HTTP, with or without data being sent;
this is an example of what it takes to send data from a WinForm to a web
server; I'm leaving out what comes back from the server; you can have your
web page send back whatever makes sense (or nothing at all); the page you
request just has to handle the data in the Request collection and dump it in
the SQL store ... simple ...

string url = "http://www.MyServer.com/DataPost.asp";;

HttpWebRequest req;
req = (HttpWebRequest)HttpWebRequest.Create(url);

// no search for proxy; takes forever
req.Proxy = null;

// create an arbitrary HTTP request header
req.AllowAutoRedirect = true;
req.UserAgent = "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR
1.1.4322)";
req.Accept = "*/*";
req.Method = "POST";
req.ContentType = "application/x-www-form-urlencoded"; // important

// you have to build up your data string from the WinForm
string postData = "var1=POSTMEISTER&var2=message";
byte[] postDataBytes = Encoding.UTF8.GetBytes(postData.ToString());

req.ContentLength = postDataBytes.Length;

Stream postDataStream = req.GetRequestStream();
postDataStream.Write(postDataBytes, 0, postDataBytes.Length);
postDataStream.Close();

Would not a
Web Service be easier because it will do all the packaging and
unpackaging of the data for me?

I think it's hard to get simpler than what I posted above ...

It is my understanding that
WebServices is simply Microsoft's version of SOAP which is simply an
interface to make function calls and to interact with classes over
HTTP. Am I mistaken?

not mistaken but over-simplified ... but I am by no means knocking web
services and if learning to write a web service to do this project is
valuable payback for taking on the project then by all means do it would be
my view







.

Relevant Pages

  • Re: Connection limit
    ... If I start the program generating threads every 200 milliseconds each wanting to call the web service. ... Sometimes these threads back up for no apparent reason and there will be for example 50 threads concurrently running each trying to make web request. ... If I have the program stop creating threads at that point, I see in Fiddler that it takes over a minute for those all of those threads to make their http calls to the web service, get their responses and end. ...
    (microsoft.public.dotnet.languages.vb)
  • Web services, JAX-RPC, SOAP and Tomcat
    ... I have genereated and used a client for my web service using JWSDP 1.5 ... I found that the content-type and accept http headers are different. ... The problem is that with the text/xml MIME-type, my request works as ... Cache-Control: no-cache ...
    (comp.lang.java.programmer)
  • Re: Events from a web service ?
    ... Perhaps HTTP chunking to get events from web service to ... Or one could issue a GetEvent request to a web service in a separate ... ASP.NET thread pool threads for large number of clients? ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Dynamic WSDL Generation
    ... that performs SSL termination. ... load balancer terminates the SSL connection and passes the request to ... the web server via http. ... This all works fine for accessing the web service itself. ...
    (microsoft.public.dotnet.xml)
  • Whats going on with Microchip?
    ... Because of that risk I requested all our customers to review their ... Many of you listened to that genuine request ... an order with Microchip for the next 8 to 12 weeks of your ... are now finding it difficult to live with even 3 to 4 week lead-times. ...
    (comp.arch.embedded)
Loading