RE: Re(2): URL Access performance tuning
RE: Re(2): URL Access performance tuning
- Subject: RE: Re(2): URL Access performance tuning
- From: "Pietrzak, Bryan" <email@hidden>
- Date: Tue, 21 May 2002 08:58:52 -0600
I guess the answer to "who cares" is me. I don't want to develop an app that
is a resource hog. If I do that and then five other developers do that then
OS X networking sucks. That's bad.
So, as a good developer I've got my algorithm working (based on URL Access)
and now I'm fine tuning.
Anyway, each time the app runs and the users goes online to play (it's a
series of card games) I make one connection to download an XML formatted
config file. This file is usually no more than 2-3K tops, so it'll be
transparent to the user.
Then, I parse this file and, as needed, download new artwork and such. So,
generally, there won't be frequent downloads, it won't be a common occurence
to change the online look and feel.
Bryan
-----Original Message-----
From: Jens Bauer [
mailto:email@hidden]
Sent: Tuesday, May 21, 2002 9:24 AM
To: Quinn; The cool guys; Pietrzak, Bryan
Subject: Re(2): URL Access performance tuning
Hi Quinn and Bryan,
On Tue, 21 May, 2002, Quinn <email@hidden> wrote:
>
At 15:18 -0600 14/5/02, Pietrzak, Bryan wrote:
>
>I'm using the URLAccess APIs in Carbon to download 1-n files from a remote
>
>HTTP server.
{snip}
>
>Basically, I
>
>guess I'm asking, how "bad" is it for me to use URL Access to download a
>
>bunch of files? Am I burning an extraordinary number of CPU cycles and
>
>wasting network resources?
>
>
I'll take a pragmatic approach and ask "How often does the user do
>
this?" If they only do it once a month for software updates, who
>
cares?
Excuse me for breaking in. ;)
I would say that if you use URLAccess, and Mac OS X gets optimized, this
would cause your application to be "optimized for free".
-This is one of the reasons, that I try using the system's frameworks as
much as possible, rather than writing my own.
Since you're downloading from a HTTP server anyway, I would probably put
my 3 cents on the URL-Access, especially if you need to have your
software ready in no time.
You'll always be able to see later, if you don't really think the
performance is good enough, *then* spend some time on finding out how you
can download a file via HTTP. (It isn't too complicated writing the code
to receive the data, but you will have to deal with the protocol itself,
such as "content-encoding: chopped", (or was it chunked ? :)), etc.)
Love,
Jens
--
Jens Bauer, Faster Software.
-Let's make the World better, shall we ?
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.