Although FTP is a reasonable method of file transfer, it isn't likely
the appropriate method of uploading OLC data. FTP has also had a
pattern of security cracks in the past few years, so SCP/SFTP tunneling
via SSH is much preferred. A file transfered via FTP would require an
additional server process, additional server ports, real server load,
and additional scripts and support issues. If would also complicate
the edit function.

Claim submissions are undoubtedly parsed to one, and likely more, data
table(s) from which the several results pages are queried. PHP is the
method of choice. Likely MySQL, PostgreSQL, or maybe even DB2, would
be likely database engines due to cost and speed.

Obvious agendas for an OLC type setup would be badge leg and record
submissions with OO/NAC endorsements. However, since most NAC's have
their own system of validations and qualifications (and in some cases,
fees), that may require some real re-work between the FAI/IGC and NAC's
to accomplish. Technically, it looks very close. Bureaucratically,
it's a ways off for some of use, closer for others. Nevertheless,
legacy support would seem to remain important, as would bug fixes in
software and firmware.

My $.02

Frank Whiteley

jcarlyle wrote:
They weren't so much "solutions" as they were examples to help Doug
understand that he was being given a line. I agree that they have an
agenda which they aren't revealing. But it isn't gaining them users, at
least at my club. Most pilots there believe that the interface and
upload procedures are just too clunky and confusing to be worth their
time.

-John


Marc Ramsey wrote:
The brush-off might have something to do with the fact that all of these
"solutions" are specific to IIS/ASP running on Windows servers, when I
believe OLC runs Apache on Linux servers. That said, binary file upload
is pretty trivial to implement using the standard mechanisms provided in
HTML/HTTP, which suggests they have other reasons for not doing so...

Marc