Where is the Activetick API document?
- Thread starter hardywu
- Start date
@hardywu
The C++ example included with SDK uses multiple inheritance for the Streamer class:
class Requestor : public ActiveTickServerRequestor
{
public:
Requestor(const APISession& session);
virtual ~Requestor(void);
..
..
class Streamer : public ActiveTickStreamListener, public Requestor
{
public:
Streamer(const APISession& session);
virtual ~Streamer(void);
..
..
This is a very typical C++ inheritance case, in which your Streamer object can send requests to the server AND also receiving streaming updates.
As always, you can send your questions related to API directly to our support at support@activetick.com
The C++ example included with SDK uses multiple inheritance for the Streamer class:
class Requestor : public ActiveTickServerRequestor
{
public:
Requestor(const APISession& session);
virtual ~Requestor(void);
..
..
class Streamer : public ActiveTickStreamListener, public Requestor
{
public:
Streamer(const APISession& session);
virtual ~Streamer(void);
..
..
This is a very typical C++ inheritance case, in which your Streamer object can send requests to the server AND also receiving streaming updates.
As always, you can send your questions related to API directly to our support at support@activetick.com
@syswizard We're a bit behind but making good progress. Our first beta release should go live within 1-2 weeks. You can request to be added to our notification list if you email support at activetick.com.
@activetick will this include L2 or is that going to be done through activeticker?
@activetick
I can confirm that, without modify the source code, the compiled binary is working without such issue in linux system. So the error comes from the shared library `libActiveTickServerAPI.dylib` for Mac OS X system. My guess would be that the `atfeed-cppsdk-osx.i386.tar.gz` SDK is casting memory errors under 64-bit Mac System.
I can confirm that, without modify the source code, the compiled binary is working without such issue in linux system. So the error comes from the shared library `libActiveTickServerAPI.dylib` for Mac OS X system. My guess would be that the `atfeed-cppsdk-osx.i386.tar.gz` SDK is casting memory errors under 64-bit Mac System.