Hi Jerry,
The TCPBroker class would work well. I could probably take that and put it in a dll or a shared object, add a factory of some sort, and then create a php extension that will translate the objects into php objects on the fly.
One of the reasons we would like to use php is because our application relies heavily on dynamic classes and types. In php the objects are inherently late bound and typeless.
Cheers,
Gardner
-----Original Message-----
From: Jerry Goodnough
Sent: Wednesday, September 18, 2002 1:11 PM
To: Gardner Bickford
Subject: EsiObjects Communications
Gardner,
At this moment the documentation for the protocol needs to be brought up to
date... If there are specific tasks that you wish to accomplish I can try to
put something meaningful together for you... Also we should most likely move
this dicussion over to SourceForge so others will be able to contribute to
it and reference it in the future.... https://sourceforge.net/projects/esiobjects/
Also I don't know if you read C++ or not, but CVS on SourceForge has Code
for the TCPBridge (A Little stale, but likely good enough for your
purposes). The TCPBroker class handles the most of the communications burden
for talking with the server.
Jerry Goodnough
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Jerry,
I have been working on porting the TCPBridge to linux, which involves replacing all the MFC, ATL, and ActiveX references in the source code. If you could give me a quick rundown on each of the classes and their role in the TCPBridge it would help me greatly. Specifically:
Hi Jerry,
The TCPBroker class would work well. I could probably take that and put it in a dll or a shared object, add a factory of some sort, and then create a php extension that will translate the objects into php objects on the fly.
One of the reasons we would like to use php is because our application relies heavily on dynamic classes and types. In php the objects are inherently late bound and typeless.
Cheers,
Gardner
-----Original Message-----
From: Jerry Goodnough
Sent: Wednesday, September 18, 2002 1:11 PM
To: Gardner Bickford
Subject: EsiObjects Communications
Gardner,
At this moment the documentation for the protocol needs to be brought up to
date... If there are specific tasks that you wish to accomplish I can try to
put something meaningful together for you... Also we should most likely move
this dicussion over to SourceForge so others will be able to contribute to
it and reference it in the future....
https://sourceforge.net/projects/esiobjects/
Also I don't know if you read C++ or not, but CVS on SourceForge has Code
for the TCPBridge (A Little stale, but likely good enough for your
purposes). The TCPBroker class handles the most of the communications burden
for talking with the server.
Jerry Goodnough
Hi Jerry,
I have been working on porting the TCPBridge to linux, which involves replacing all the MFC, ATL, and ActiveX references in the source code. If you could give me a quick rundown on each of the classes and their role in the TCPBridge it would help me greatly. Specifically:
EoErrorException
ESITCPData
EventManager
EventMapMgr
EvtObjMap
ObservationList
RequestFailedException
ServiceSink
TCPArchive
TCPBroker
WatchInfo
WatchTracker
Thanks,
Gardner