From: Anthony Sorace <a@9srv.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Fedex command
Date: Thu, 31 May 2012 10:38:57 -0400 [thread overview]
Message-ID: <067D6E51-1C58-4B73-8E84-B32C39E3AE99@9srv.net> (raw)
In-Reply-To: <30883906.151136.1338474262277.JavaMail.root@vms170035>
[-- Attachment #1: Type: text/plain, Size: 504 bytes --]
The fedex command (like ups and usps) work by scraping the HTML on the
public web site. That changes fairly often, and fedex & co need updates each
time. It's not terribly difficult, but it's tedious and frequent. I end up tweaking
these about every other time I want to track a package.
Most (all?) such places provide actual RESTish APIs to use, but those require
(generally free) keys/accounts. After my last round of tweaking fedex I took a
stab at rewriting it to use those, but stalled.
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 210 bytes --]
next prev parent reply other threads:[~2012-05-31 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 14:24 V. M. (Mark) Haas
2012-05-31 14:38 ` Anthony Sorace [this message]
2012-05-31 16:31 V. M. (Mark) Haas
2012-05-31 18:23 ` Anthony Sorace
2012-05-31 20:55 ` steve
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=067D6E51-1C58-4B73-8E84-B32C39E3AE99@9srv.net \
--to=a@9srv.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).