The Builder pattern always hides the method of creation from the client code and it resided at the object itself that u wanted to create. if u would like to compose different object that has same kind of template, u always can use Template pattern for abstract together with Composite pattern for the tree type linking. To create this composite pattern you always has Factory method pattern to assist you to reach to the Builder pattern for creation during run time.
The whole thing u assemble it together should be called Compound Patterns.
Remember to use back all standard terms unless you really has created a new way of approach to the design pattern. My intention is not to mislead developers...
the pattern "language" that i mention above(title) is not programming language, but the way we communicate to each other in developers community. Anyone could discuss the finding or works but one should use back the standard term instead of creating new terms to explain.
i wish to replace callback by template specialisation.
is anyone come to this b4 and knowing that is multi-thread safe?
my application goes like this, many instance from our working code
is registering function pointer(for callback) to the library.
so that the library will notify us whenever it completed its job.
the answer to this question was found in the book, Complete Guide to Template Programming.
the specialise template can reside at client code, it actually override the abstract
template in the library. During compilation time, the linker will check is there a specialise
template defined and link accordingly.
1. "Three ways to inject your code into another process" by Robert Kuster.
2. "Remote Library" by António Feijão.
3. "PrcHelp" by Radim Picha.
4. "Windows 95 System Programming Secrets" by Matt Pietrek.
5. "Windows NT/2000 Native API Reference" by Gary Nebbett.
6. "A Crash Course on the Depths of Win32 Structured Exception Handling" by Matt Pietrek.
7. "Enumerating Windows Processes" by Alex Fedotov.
For Win9x stuff see  (99 % of the Win9x code comes from this book).
I don't know any equivalent book for NT, but two usefull books (not directly related to remote code injection) are:
- "Undocumented Windows NT" by P. Dabak, M. Borate, S. Phadke (http://www.windowsitlibrary.com/Documents/Book.cfm?DocumentID=356)
- "Microsoft Windows Internals, 4th ed." by M. Russinovich, D. Solomon
-= aLbert =-
Last Visit: 31-Dec-99 19:00 Last Update: 22-Nov-14 19:08