Friday, July 29, 2005

ECMA

Ecma International is an industry association founded in 1961 and dedicated to the standardization of Information and Communication Technology (ICT) and Consumer Electronics (CE).

Itt van az lista

nehany pelda:
ECMA-334 C# Language Specification, 3rd edition (June 2005) [pdf]

ECMA-335 Common Language Infrastructure (CLI), 3rd edition (June 2005) [pdf]

ECMA-367 Eiffel analysis, design and programming Language (June 2005) [pdf]

Sunday, July 24, 2005

The Puzzlet Page

Enjoy mental workouts?
Use maths occasionally?
Like numerical brainteasers?
Revel in intellectual challenges?
Dabble in computer programming?

Answer "yes" to any of the above, and you've come to the right place!

What is a Puzzlet?

A mathematical problem which will almost always require the use of a simple computer program to solve.

You will need at least a rudimentary knowledge of maths to solve it, and occasionally more. You can use this skill to understand the problem, derive a formula to resolve it if necessary, and define the range within which the answer should fall.

At this stage, you will usually be unable to derive an exact answer, and will have to resort to a simple computer program to go further. You'll have to develop an algorithm, write the code, debug it, and get it to run.

Finally, you need to test your answer for accuracy and completeness. Many Puzzlets have several answers, and part of the challenge is to be sure you've found them all. That, then, is the complete Puzzlet experience!

Itt van peldaul a 151-es:
Look at the prime number 3137. If one digit at a time is deleted, we generate the "sub-numbers" 137, 337, 317, 313. All four new of the sub-numbers are also prime,or sub-primes. Are there any more 4-digit primes which behave in exactly the same way?

Friday, July 22, 2005

Paul J. Leach: UUIDs and GUIDs (February 4, 1998)

This specification defines the format of UUIDs (Universally Unique IDentifier), also known as GUIDs (Globally Unique IDentifier).

Raymond Chen: Computing the size of a directory is more than just adding file sizes

One might think that computing the size of a directory would be a simple matter of adding up the sizes of all the files in it.

Oh if it were only that simple.

There are many things that make computing the size of a directory difficult, some of which even throw into doubt the even existence of the concept "size of a directory".

Itt van a listaja.

Tuesday, July 19, 2005

Scott Mitchell: What Are .NET Web Services?

Itt van a ppt file es itt a blog bejegyezese.

This talk will examine the fundamentals of Web services from a beginner's perspective, focusing on the goals of Web services and common uses of Web services in industry today. It Includes a high-level look at the core Web service standards, along with live demos illustrating how to create a Web service and client application using Visual Studio .NET.

Windows File System Tunneling

Windows NT Contains File System Tunneling Capabilities:

When a name is removed from a directory (rename or delete), its short/long name pair and creation time are saved in a cache, keyed by the name that was removed. When a name is added to a directory (rename or create), the cache is searched to see if there is information to restore. The cache is effective per instance of a directory. If a directory is deleted, the cache for it is removed.

These paired operations can cause tunneling on "name".
- delete(name)/create(name)
- delete(name)/rename(source, name)
- rename(name, newname)/create(name)
- rename(name, newname)/rename(source, name)

The idea is to mimic the behavior MS-DOS programs expect when they use the safe save method. They copy the modified data to a temporary file, delete the original and rename the temporary to the original. This should seem to be the original file when complete. Windows performs tunneling on both FAT and NTFS file systems to ensure long/short file names are retained when 16-bit applications perform this safe save operation.
...
Tunneling cache time can be adjusted from the default time of 15 seconds, or if tunneling capabilities are undesirable, it can be disabled by adding a value in the Windows Registry.

A fenti cikk innen van:
Raymond Chen: The apocryphal history of file system tunnelling

O ezt irja meg:

As another example of the importance of tunneling, consider that file "File with long name.txt", whose short name is say "FILEWI~1.TXT". You load this file into a program that is not long-filename-aware and save it. It deletes the old "FILEWI~1.TXT" and creates a new one with the same name. Without tunnelling, the associated long name of the file would be lost. Instead of a friendly long name, the file name got corrupted into this thing with squiggly marks. Not good.

Illetve leirja, hogy a tunneling kifejezes a quantum mechanikabol lett atveve.

Monday, July 18, 2005

Andrew D. Birrell: An Introduction to Programming with C# Threads

Itt van a pdf (41 oldal).

CONTENTS
1. Introduction
2. Why use concurrency?
3. The design of a thread facility
4. Using Locks: accessing shared data
5. Using Wait and Pulse: scheduling shared resources
6. Using Threads: working in parallel
7. Using Interrupt: diverting the flow of control
8. Additional techniques
9. Advanced C# Features
10. Building your program
11. Concluding remarks

Wednesday, July 13, 2005

hpirate - konyvek magyarul

Van itt egy halom konyv, de nem tunik tul legalisnak.

Saturday, July 09, 2005

Mérő László: A játékelmélet és a racionalitás pszichológiája (Élet és Tudomány - Sulinet)

Amikor egy hosszú sorozat végére pontot tesz a szerkesztő, természetesen egy kicsit büszke: a lap történelme ismét gazdagabb lett egy fejezettel. De némi szomorúságot is érez, még ha közben a mindenki másképp egyforma könyv alakban is megjelent, s olvasónknak igy bőségesen módjában áll kalandozni a játékelmélet és a racionalitás pszichológiája világában. Mérő László lapunkban nem művének zanzáját közölte, hanem alkalmasan kiválasztott részleteiből egy önálló ívet épített.

1. A Dollárárverés ördögi spirálja
2. A pózolás
3. Marsbéli etikák
4. A főszereplő megjelenik
5. A fogoly dilemmája
6. A közlegelők problémája
7. Fogolydilemmák az életben
8. Az aranyszabály és a szeretet csapdái
9. „Az értelemig és tovább...”
10. Jobb ma egy veréb?
11. Kollektív racionalitás
12. Nem mind fénylik, ami arany
13. Sok út vezet a nirvánába

Wednesday, July 06, 2005

[ingyen konyv] Andrew Troelsen: COM and .NET Interoperability

Apress Publishing has provided TheServerSide.NET with COM and .NET Interoperability for free download.

"COM and .NET Interoperability" covers working with COM components in .NET and .NET components in COM from basic topics like Runtime Callable Wrappers to advanced topics such as manual marshaling of data types between .NET and COM. This book is available in its entirety as a download to registered TSS.NET readers.


Download the FREE Book

Contents:

Chapter 1 Understanding Platform Invocation Services
Chapter 2 The Anatomy of a COM Server
Chapter 3 A Primer on COM Programming Frameworks
Chapter 4 COM Type Information
Chapter 5 The Anatomy of a .NET Server
Chapter 6 .NET Types
Chapter 7 .NET-to-COM Interoperability — The Basics
Chapter 8 .NET-to-COM Interoperability — Intermediate Topics
Chapter 9 .NET-to-COM Interoperability — Advanced Topics
Chapter 10 COM-to-.NET Interoperability — The Basics
Chapter 11 COM-to-.NET Interoperability — Intermediate Topics
Chapter 12 COM-to-.NET Interoperability — Advanced Topics
Chapter 13 Building Serviced Components (COM+ Interop)

[ingyen konyv] Aaron Skonnard, Martin Gudgin: Essential XML Quick Reference

Essential XML Quick Reference: A Programmer's Reference to XML, XPath, XSLT, XML Schema, SOAP, and More

Addison-Wesley and Developmentor have provided TheServerSide.NET with the entire book of Essential XML Quick Reference for free download. Essential XML Quick Reference is for anyone working with today's mainstream XML technologies. It was specifically designed to serve as a handy but thorough quick reference that answers the most common XML-related technical questions.It goes beyond the traditional pocket reference design by providing complete coverage of each topic along with plenty of meaningful examples. Each chapter provides a brief introduction, which is followed by the detailed reference information. This approach assumes the reader has a basic understanding of the given topic.The detailed outline (at the beginning), index (in the back), bleeding tabs (along the side), and the page headers/footers were designed to help readers quickly find answers to their questions.


Download the FREE PDF

Tuesday, July 05, 2005

Eric Lippert: What Are "Anonymous Functions" In JScript?

Itt van.

Justin Rogers: Understanding and Solving Internet Explorer Leak Patterns

In the past, memory leaks haven't posed huge problems for Web developers. Pages were kept relatively simple and navigation between different locations within a site was a great way to clean up any loose memory. If there was a leak, it was most likely small enough to go unnoticed.

New Web applications live up to higher standards. A page might run for hours without being navigated and retrieve updated information dynamically through Web services. Language features are pushed to the breaking point by combining complex event schemes, object-oriented JScript, and closures to produce entire applications. With these and other changes, certain memory leak patterns are becoming more prominent, especially those previously hidden by navigation.

The good news is that memory leak patterns can be easily spotted if you know what to look for. Most of the troublesome patterns you might face have known workarounds requiring only a small amount of extra work on your behalf. While some pages might still fall prey to small memory leaks, the most noticeable ones can be easily removed.

The following sections will discuss patterns of memory leaks and point out some common examples of each pattern.:

Circular References — When mutual references are counted between Internet Explorer's COM infrastructure and any scripting engine, objects can leak memory. This is the broadest pattern.

Closures — Closures are a specific form of circular reference that pose the largest pattern to existing Web application architectures. Closures are easy to spot because they rely on a specific language keyword and can be searched for generically. Eric Lippert, one of the developers of the scripting engines, has a great post on closures in general.

Cross-Page Leaks — Cross-page leaks are often very small leaks of internal book-keeping objects as you move from site to site. We'll examine the DOM Insertion Order issue, along with a workaround that shows how small changes to your code can prevent the creation of these book-keeping objects.

Pseudo-Leaks — These aren't really leaks, but can be extremely annoying if you don't understand where your memory is going. We'll examine the script element rewriting and how it appears to leak quite a bit of memory, when it is really performing as required.

In the interest of patterns and design I highly recommend Scott's short blog entry because it demonstrates a general purpose example of removing all closure-based leaks.

Innen jott a link: Joel Webber: Another Word or Two on Memory Leaks