Re: Problem sending data with CFHTTPMessage
Re: Problem sending data with CFHTTPMessage
- Subject: Re: Problem sending data with CFHTTPMessage
- From: Dan Korn <email@hidden>
- Date: Wed, 18 Mar 2009 18:17:49 -0500
Hi David! I've finally found a kindred soul, someone who understands
me! We're in the same boat here, trying to maintain an Acrobat plug-
in across all the wonderful variations of operating systems, APIs, and
development tools that both Apple and Adobe keep throwing at us (and
Microsoft too, but they don't decide to reinvent the whole universe
quite as often). Just when you get something working for Acrobat 6
under CFM in CodeWarrior for OS 9, OS X comes along and you get to
port it to Carbon, and then Acrobat 7 comes along with Mach-O, then
Acrobat 8 with Universal Binary and you get thrown into Xcode. And
along the way you get to unlearn everything you've learned and re-
learn it all again. Paths are evil, no, paths are good; use HFS, no,
use POSIX. Carbon is the future, no, Cocoa is the future. You need
to port from QuickDraw to Quartz; from GrafPorts to HIViews to NIBs to
xibs; from dylibs to frameworks; from little-endian to big-endian back
to little-endian, to Leopard, to Tiger, to lions, and bears, oh my!
And you get to port from ADM to, well, whatever you can cobble
together to put up a dialog since Adobe decided to drop ADM. And hey,
good work porting everything to the latest and greatest OS and all,
but your customers still use old machines, so you can't take advantage
of all the super-cool new features and fixes that actually make the
debugger reliable in Xcode 3 because you still need to build for
Tiger. If you're really lucky, you're still using CodeWarrior for
part of your build because you haven't had time to port everything,
not to mention do anything like, say, add new features to your
product, because you've been trying to hang on by your little pinky
finger to Apple's yacht which is constantly motoring towards the
horizon of ever-newer technologies (hello iPhone!), dragging Adobe and
everyone else along with them. Supporting Acrobat 9 hasn't been as
much of an effort (for me) compared to the ports for the last few
versions, but hey, it's all job security, right?
</rant> Whew, that feels better!
Anyway, my advice is to put as much functionality as possible into an
external application that's not part of your Acrobat plug-in. Make
yourself a standalone registration utility program, which you can
build with any toolkit and on any base technology (Carbon, Cocoa,
OpenTransport, CFHTTP) you want, and go with it as long as you can
until that underlying technology is completely unsupported, then skip
a few generations and port it to the new stuff. Send an Apple Event
to your external registration program, or make it a Unix utility and
send it command-line parameters (extra credit for putting the app in
your plug-in's bundle), whatever works. The idea is to divorce that
piece of functionality from whatever new Apple technology Adobe
decides to use in the next version of Acrobat, so that it doesn't
suddenly break for reasons that may well be impossible to discern, let
alone fix.
Dan
On Mar 17, 2009, at 3:06 PM, David Gagnon wrote:
Hi,
We are using Xcode to develop an Acrobat plug-in in C++. To send an
http
registration information, we are using CFHTTPMessage (based on POST
Example
from Apple)... And it does not work well all the time, especially
when our
plug-in is running into Acrobat 9 (it is working in Acrobat 8).
Sometimes,
we received kCFStreamEventEndEncountered in ReadStreamClientCallBack
and
sometimes we received nothing. Also, we discovered that turning on
and off
the firewall can fix the problem but for 1 time only.
Do you know if the fact that our product is a plug-in can be the
cause of
the problem?
Do you know if the application signature of Acrobat is changed when
our
plug-in is copied into Acrobat?
Any idea about the source of the problem is very appreciated...
Note that we are using OSX 10.5 on iMac Intel.
Thanks!
David
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden