Implementing the transport layer for a SIP UAC

I have a somewhat simple, but specific, question about implementing the transport layer for a SIP UAC.

Progressbar patterns (Eclipse)

I’ve struggled quite a bit with Eclipse and progress-monitors to try to have good progressbars which report useful progress information to the user. Inevitably the code gets cluttered with lots of things like

doing a full permutation search and replace on a string

I’m writing an app that does something like a custom number (license) plate generator tool where if I ask for the plate “robin” it will suggest I try:

Creating a Predicate Builder extension method

I have a Kendo UI Grid that I am currently allowing filtering on multiple columns. I am wondering if there is a an alternative approach removing the outer switch statement?

Should I use the factory design pattern for every class?

I’ve been writing a website in PHP. As the code becomes more complex, I keep finding problems that can be solved using the factory design pattern. For example: I’ve a got a class Page which has subclasses HTMLPage, XMLPage, etc. Depending on some input I need to return an object of either one of these classes. I use the factory design pattern to do this.

Use decorator and factory together to extend objects?

I’m new to OOP and design pattern.

What is the best way to compose an object with components across two assemblies?

In my project, I have a collection of classes. These classes for the most part contain data which is updated infrequently or not at all – that is they don’t really do much – their purpose is to be passed around consumer objects that do do things, seperating data from functionality.

Are monolith and microkernel design patterns or strategies?

What’s the difference between a design pattern and a strategy?
Is the monolith actually an anti-pattern?

Representing complex object dependencies

I have several classes with a reasonably complex (but acyclic) dependency graph. All the dependencies are of the form: class X instance contains an attribute of class Y. All such attributes are set during initialization and never changed again.

How to avoid big and clumsy UITableViewController on iOS?

I have a problem when implementing the MVC-pattern on iOS. I have searched the Internet but seems not to find any nice solution to this problem.