Subject:
|
Re: Automatic download of unofficial parts in LDView
|
Newsgroups:
|
lugnet.cad.dev.org.ldraw
|
Date:
|
Wed, 17 May 2006 18:33:18 GMT
|
Viewed:
|
2118 times
|
| |
|
|
In lugnet.cad.dev.org.ldraw, Travis Cobbs wrote:
> In lugnet.cad.dev.org.ldraw, Dan Boger wrote:
> > Sounds reasonable. Perhaps it might be more efficient (for the client)
> > to send just one request with a list of files it needs, and have the
> > server return all the ones that are found? That should make the whole
> > operation faster, since it'll be just one HTTP request/reply, instead of
> > (potentially) hundreds.
>
> That starts getting more difficult for a few reasons. First of all, the tracker
> would have to return all the dependent files on the tracker in addition to the
> requested files. Many of these files could well be already present on the
> end-user's machine.
I'd say it wouldn't *have* to return the dependent files. LDView can turn
around, and make an additional request.
> Secondly, from an architectural perspective, LDView doesn't have an easy way to
> produce the list. The code that I have right now checks the tracker any time it
> gets to a reference to a part file that it can't find.
Well, the server can support multiple files per request, and client programs can
use it as well as they can.
> We'd also have to agree on a format for the response containing the multiple
> files.
Use MPD (within a text response). Sending a stream of multiple files was the
original purpose of the MPD format.
Steve
|
|
Message has 1 Reply:
Message is in Reply To:
26 Messages in This Thread:
 
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
