× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




Can you still use the exit points if you want to?

Yes. Cookie support is turned off by default (http_use_cookies(*YES) is needed to turn it on.) and the exit points are still available, so if you don't make any changes, it'll still work.

However, my cookie code does all of the following. I don't know if I've seen yours before, but it may not have as many features...

-- Handles path qualifiers on the cookies, only sending back when appropriate.
-- Expires cookies from the cache
-- Understands when the server is attempting to delete a cookie from the cache, and deletes it as appropriate.
-- Handles both version 0 and version 1 cookies
-- Handles domain names & subdomains and sends cookies back only when appropriate.
-- Understands the difference between persistent and temporary cookies.
-- Allows you to save the cookies to disk so that persistent (non-temporary) cookies can be saved from session to session.

Granted, all of these features are pretty much standard in all browsers, but the exit point code that I've seen people use with HTTPAPI, usually doesn't incorporate them all.

Granted, chaning the code in the application exit points to the line above is pretty minor but if I don't upgrade right away and forget to change the source in my application will it continue to work with the new HTTPAPI or is it not backward-compatible? My guess is that it would continue to work.

I always strive to keep in backward compatible. It should work without any re-compiling or re-binding (much less changing the code!) if it doesn't, it's a bug and should be reported to the FTPAPI list.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.