R. Clayton (rclayton@clayton.cs.monmouth.edu)
(no date)
We are trying to figure out how the client knows whether to post or get a
file from the server.
That depends on the operation the client is sending to the server and how your
protocol implements the operation. If you're implementing an andrew-sprite
style whole-file caching protocol, then gets would probably be better. If
you're implementing an nfs-style protocol, then posts are probably better.
In general, and given the client-side api, I'm thinking posts are easier than
gets, but it's up to you.
Is there a parameter we are suppose to send when calling the client:
server_ip_address server_ip_address server_port_number@file post or getfile?server server_ip_address server_port_number@file post or getfile?server port@file
where this command is typed into the command line.
I'm not following you here; who is the "we" calling the client? The
client-side api implementation should hide all the details of posts and gets
(and all other http details) from the client-side api caller
This archive was generated by hypermail 2.0b3 on Sun May 06 2001 - 20:30:05 EDT