Home/ Questions/Q 6384503
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T02:47:03+00:00

Background: I am about to start preparing my 1st framework for my clients, so

  • 0

Background: I am about to start preparing my 1st framework for my clients, so they can easily integrate it into their apps and fetch data from my servers without dealing how communication with server is working. I chose ASIHTTPRequest library for communication.

Question: how should I deal with ASIHTTPRequest or any other static library – make it a part of my framework or let adopters link against it themselves in their projects?

I’m opting to make it a part of my framework, so I can prevent users from setting breakpoints in ASIHTTPRequest and easily access/log connection frames/data. But what would happen if my clients will need this library for their own purposes? Will they be able to link it second time? Won’t it cause any run-time collisions?

Sorry for wording… Please let me stand corrected if I’m confusing any terms 🙂

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    There are two different types of frameworks to consider, so I would do two things:

    1. For any third party library like ASI that you use, include a
      directory with the source as deanWombonurne indicated. Make sure to indicate which version of the library you have included if it is not clear (add a VERSION) file if needed or name the directory).

    2. For Apple frameworks, include a manifest file somewhere that gives a
      list of all the Apple frameworks they should include in their
      project to satisfy your framework requirements.

    • 0