Sending Email To The Future Date

Sending Email To The Future Date

Use Link - http://www.whensend.com/

Other Websites:

1. http://www.rightinbox.com/

2. www.futureme.org

How Does Satellite TV Work?

While you may hear about DISH satellite service or even be a DISH customer, have you ever really thought about satellite TV works? How does that dish on your roof or in your backyard bring you TV shows, movies and music from all over the world? Here is a brief explanation of how satellite technology brings television programming into your home 24 hours a day, seven days a week.

Satellite Technology—Past and Present

In the past (early 1990’s), satellite dishes were very big and bulky and often seen as eyesores in people’s backyards. Also, satellite dishes were often associated with rural living, and “city dwellers” did not realize the many advantages of satellite TV over cable. Satellite dishes also got a bad rap for losing their signal in inclement weather situations (heavy rain, wind or snow). Another past issue for satellite dishes was that to stay in sync with satellites, they had to be adjusted fairly often—which meant someone in the household had to manually adjust the position to receive a better signal.
But just like all the other technologies that have evolved since the early ‘90s (think giant brick-sized cell phones) satellite technology has made leaps and bounds too.
With so many advances in technology, satellite dishes are now very small and don’t require any adjustments by the subscriber.  Now, satellites are fixed in a geosynchronous orbit, which means they move with the Earth and are fixed in a certain part of the sky. As long as your satellite dish stays in the alignment your installer set up (facing the southern sky), you will get a clear, consistent signal. Satellites are actually an extremely efficient way of broadcasting signals because one satellite signal can provide content to such a large area of the country without the impediment of needing physical cable connections like cable companies do.

Satellite Technology Components

Here is where this gets technical.
All satellite programming is now digital, which means it has better sound and picture quality; early satellite television was broadcast in C-band radio (radio in the 3.7 gigahertz to 6.4 gigahertz range). Digital broadcast satellite transmits programming in what is called the Ku frequency range (11.7 GHz to 14.5 GHz). There are five components to satellite TV technology:

1. Programming source—These are the channels that provide programming for broadcast. DISH does not create original programming. It pays other companies (ESPN or Showtime®, for instance) for the right to broadcast their content via satellite, so the provider (in this case, DISH) is the “middleman” between the actual programming source and you, the customer.
2. Broadcast center—This is the central hub of the system and where the TV provider (i.e. DISH) receives signals from programming sources (HBO®, CNN, etc.) and beams a broadcast signal to satellites in orbit.
3. Satellites—Receive the signals and rebroadcast them back down to Earth.
4. Satellite dish—Picks up the signal from the satellites in the sky and passes it on to the receiver in your home.
5. Receiver—Processes the signal and passes it on to a television set.

If you’ve ever wondered, “How does satellite TV work?” you now have your answer! Satellite TV really is an amazing system to get programming into your home (or on your mobile device with TV Everywhere™ technology). As long as you have a view of the southern sky, there is a satellite signal just waiting for you to have a dish and a receiver to pick it up.
DISH’s customer service team stands ready to answer all of your questions if you’re considering making the switch to DISH. New DISH customers get great DISH deals like free standard installation, free premium channels for 3 months, HD Free for Life, and Blockbuster.

Window Communication Foundation(WCF Technology)

Windows Communication Foundation (WCF) is a framework for building service-oriented applications. Using WCF, you can send data as asynchronous messages from one service endpoint to another. A service endpoint can be part of a continuously available service hosted by IIS, or it can be a service hosted in an application. An endpoint can be a client of a service that requests data from a service endpoint. The messages can be as simple as a single character or word sent as XML, or as complex as a stream of binary data. A few sample scenarios include:

• A secure service to process business transactions.
• A service that supplies current data to others, such as a traffic report or other monitoring service.
• A chat service that allows two people to communicate or exchange data in real time.
• A dashboard application that polls one or more services for data and presents it in a logical presentation.
• Exposing a workflow implemented using Windows Workflow Foundation as a WCF service.
• A Silverlight application to poll a service for the latest data feeds.

While creating such applications was possible prior to the existence of WCF, WCF makes the development of endpoints easier than ever. In summary, WCF is designed to offer a manageable approach to creating Web services and Web service clients.

Features of WCF

WCF includes the following set of features. For more information, see WCF Feature Details.

• Service Orientation
  One consequence of using WS standards is that WCF enables you to create service oriented applications. Service-oriented architecture (SOA) is the reliance on Web services to send and receive data. The services have the general advantage of being loosely-coupled instead of hard-coded from one application to another. A loosely-coupled relationship implies that any client created on any platform can connect to any service as long as the essential contracts are met.
• Interoperability
  WCF implements modern industry standards for Web service interoperability. For more information about the supported standards, see Interoperability and Integration.
• Multiple Message Patterns
  Messages are exchanged in one of several patterns. The most common pattern is the request/reply pattern, where one endpoint requests data from a second endpoint. The second endpoint replies. There are other patterns such as a one-way message in which a single endpoint sends a message without any expectation of a reply. A more complex pattern is the duplex exchange pattern where two endpoints establish a connection and send data back and forth, similar to an instant messaging program. For more information about how to implement different message exchange patterns using WCF see Contracts.
• Service Metadata
  WCF supports publishing service metadata using formats specified in industry standards such as WSDL, XML Schema and WS-Policy. This metadata can be used to automatically generate and configure clients for accessing WCF services. Metadata can be published over HTTP and HTTPS or using the Web Service Metadata Exchange standard. For more information, see Metadata.
• Data Contracts
  Because WCF is built using the .NET Framework, it also includes code-friendly methods of supplying the contracts you want to enforce. One of the universal types of contracts is the data contract. In essence, as you code your service using Visual C# or Visual Basic, the easiest way to handle data is by creating classes that represent a data entity with properties that belong to the data entity. WCF includes a comprehensive system for working with data in this easy manner. Once you have created the classes that represent data, your service automatically generates the metadata that allows clients to comply with the data types you have designed. For more information, see Using Data Contracts
• Security
  Messages can be encrypted to protect privacy and you can require users to authenticate themselves before being allowed to receive messages. Security can be implemented using well-known standards such as SSL or WS-SecureConversation. For more information, see Windows Communication Foundation Security.
• Multiple Transports and Encodings
  Messages can be sent on any of several built-in transport protocols and encodings. The most common protocol and encoding is to send text encoded SOAP messages using is the HyperText Transfer Protocol (HTTP) for use on the World Wide Web. Alternatively, WCF allows you to send messages over TCP, named pipes, or MSMQ. These messages can be encoded as text or using an optimized binary format. Binary data can be sent efficiently using the MTOM standard. If none of the provided transports or encodings suit your needs you can create your own custom transport or encoding. For more information about transports and encodings supported by WCF see Transports in Windows Communication Foundation.
• Reliable and Queued Messages
  WCF supports reliable message exchange using reliable sessions implemented over WS-Reliable Messaging and using MSMQ. For more information about reliable and queued messaging support in WCF seeQueues and Reliable Sessions.
• Durable Messages
  A durable message is one that is never lost due to a disruption in the communication. The messages in a durable message pattern are always saved to a database. If a disruption occurs, the database allows you to resume the message exchange when the connection is restored. You can also create a durable message using the Windows Workflow Foundation (WF). For more information, see Workflow Services.
• Transactions
  WCF also supports transactions using one of three transaction models: WS-AtomicTtransactions, the APIs in the System.Transactions namespace, and Microsoft Distributed Transaction Coordinator. For more information about transaction support in WCF see Transactions [from BPUEDev11].
• AJAX and REST Support
  REST is an example of an evolving Web 2.0 technology. WCF can be configured to process "plain" XML data that is not wrapped in a SOAP envelope. WCF can also be extended to support specific XML formats, such as ATOM (a popular RSS standard), and even non-XML formats, such as JavaScript Object Notation (JSON).
• Extensibility
  The WCF architecture has a number of extensibility points. If extra capability is required, there are a number of entry points that allow you to customize the behavior of a service. For more information about available extensibility points see Extending WCF.

WCF Integration with Other Microsoft Technologies

WCF is a flexible platform. Because of this extreme flexibility, WCF is also used in several other Microsoft products. By understanding the basics of WCF, you have an immediate advantage if you also use any of these products.

The first technology to pair with WCF was the Windows Workflow Foundation (WF). Workflows simplify application development by encapsulating steps in the workflow as “activities.” In the first version of Windows Workflow Foundation, a developer had to create a host for the workflow. The next version of Windows Workflow Foundation was integrated with WCF. That allowed any workflow to be easily hosted in a WCF service; you can do this by automatically choosing the WF/WCF a project type in Visual Studio 2012.

Microsoft BizTalk Server R2 also utilizes WCF as a communication technology. BizTalk is designed to receive and transform data from one standardized format to another. Messages must be delivered to its central message box where the message can be transformed using either a strict mapping or by using one of the BizTalk features such as its workflow engine. BizTalk can now use the WCF Line of Business (LOB) adapter to deliver messages to the message box.

Microsoft Silverlight is a platform for creating interoperable, rich Web applications that allow developers to create media-intensive Web sites (such as streaming video). Beginning with version 2, Silverlight has incorporated WCF as a communication technology to connect Silverlight applications to WCF endpoints.

Microsoft .NET Services is a cloud computing initiative that uses WCF for building Internet-enabled applications. Use .NET Services to create WCF services that operate across trust boundaries.

The hosting features of Windows Server AppFabric application server is specifically built for deploying and managing applications that use WCF for communication. The hosting features includes rich tooling and configuration options specifically designed for WCF-enabled applications.

Upcoming Technologies

7. Firefox OS

iOS and Android are great, but they each have their own rules and policies that certainly inhibit the creative efforts of developers. Mozilla has since decided to build a new mobile operating system from scratch, one that will focus on true openness, freedom and user choice. It’s Firefox OS.

Firefox OS is built on Gonk, Gecko and Gaia software layers – for the rest of us, it means it is built on open source, and it carries web technologies such as HTML5 and CSS3.

(Image Source: Mozilla)

Developers can create and debut web apps without the blockade of requirements set by app stores, and users could even customize the OS based on their needs. Currently the OS has made its debut on Android-compatible phones, and the impression so far, is great.

You can use the OS to do essential tasks you do on iOS or Android: calling friends, browsing web, taking photos, playing games, they are all possible on Firefox OS, set to rock the smartphone market.

Track Down Elusive Network Problems

Diagnosing the Problem

The most common assumption in this situation is that the management software is faulty. Many proactive management tools connect to and manage your systems, but sometimes these tools themselves can cause the problem you're trying to track down. That's because a proactive management tool can spawn thousands of connections to your devices in the name of better management. Windows® will keep these connections open for two minutes by default even when the connections are idle, unless the tool, application, or service keep them alive longer. This means that even though your management system has not spoken to any machines in two minutes, you may still have more than 1,000 connections open. (You can view open connections by running NETSTAT in a command prompt. The NETSTAT command will show you all open, pending, and closing connections to and from your system and give you their status. Descriptions of the status messages can be found within RFC 793 at tools.ietf.org/html/rfc793.)

To rule out malfunctioning management software, you can create a batch file that establishes connections to the remote systems. If the same problem occurs while running the batch file, you'll know the management software and its threads were not to blame. Here's an example of the required batch file's contents:

Copy Code

Net use \\system01\ipc$
Net use \\system02\ipc$
Net use ...

If the management program in question happened to implement its own networking and authentication stack, it might have been the culprit, but in agentless solutions like most of these management packages, the tool uses the operating system's networking and authentication stacks to perform network operations. Using a batch file that launches just as many network connections without causing the failure will show that the issue is not a result of the program's use of the operating system's networking and authentication stacks, as the batch file uses them as well.

Logs and Error Messages that Don't Help

You may have noticed that as the connections began to fail, you received erroneous failure information: error 53—network path not found, error 64—the network name was deleted, and error 1203—no network provider accepted the given network path. All of these might normally indicate name resolution issues, except that all other machines are not having any problems resolving names and connecting to the same systems. To verify that your machine settings are not at fault, simply run ipconfig to confirm that your settings are correct.

Next, as the phenomenon seems to be localized to your management system, you should look at the event logs. A search of the application logs bears no fruit, yet in the system log you find a warning event 4226 from event source TCP/IP stating that the maximum number of connections had been reached (see Figure 1).

Figure 1 TCP connection limit has been reached 

Conducting a through search of the Microsoft® Knowledge Base for connection limits will reveal the fact that there are connection limitations imposed on incomplete connections, but there are no limits placed upon completed connections. You have the ability to adjust the following registry entries under HKLM\System\CurrentControlSet\Services\TCPIP\Parameters to control the aforementioned factors: TcpNumConnections is used to set the maximum number of connections that TCP can have open at the same time (the default is 10). TCPTimedWaitDelay sets the time a connection stays in the TIME_WAIT state when it is closing. The default half-life is 120 seconds, which means a connection is essentially in use for 4 minutes. Finally, MaxFreeTcbs also plays a role in the maximum number of connections. If all TCP control blocks are in use, TCP should release connections listed as being in a TIME_WAIT state to create more connections even though the TCPTimedWaitDelay has not yet expired. TCPTimedWaitDelay has a value range of 30-300 seconds (0x1E – 0x12C).

Depending on your scenario, you may see a slight improvement in overall performance by making these registry changes.

Network Captures

After other unsuccessful attempts to solve the connection issues, a network capture from the machines involved seems promising. When I ran Microsoft Network Monitor (Netmon), it produced captures that displayed the exact results that I was seeing in the management tools and the test scripts: everything works and then it doesn't, without any further indication of error.

Figure 2 shows the result of running Netmon, which indicated successful communication between the first n systems. Note that I'm obtaining acknowledgments of RPC requests. This is what you want to see—successful two-way communication.

Figure 2 Successful communication in Netmon (Click the image for a larger view)

Now you need to look at the captures from the management system and the remote machines that appear to exhibit the error 53/1203. As you might expect, there is nothing to see, as the machines are not communicating. In the network capture in Figure 3, the management system has resolved the IP address and attempts to connect to the system over port 445 (the Microsoft SMB port) but never receives a response.

Figure 3 Attempts to connect to the system over port 445 yield no response (Click the image for a larger view)

The error you receive when you have more threads than your machine can currently connect to is not always consistent. In some cases, you may see from the source system an error 53, indicating that you received name resolution but that the IP address simply could not be found. This is indicative of DNS providing an address to which you cannot connect. You may receive an error 1203, indicating that no machine responded to the name or IP address that you requested. Error 1203, in this case, indicates that DNS is unavailable to you. You'll see that's the case if you run nslookup.

At this point you're bound to be frustrated, but there are more options to consider. Most people will not even think to look at the connecting infrastructure because of the way in which this problem presents itself: your machine is the only one that cannot connect to the rest of the network and the event logs show your machine has reached the maximum number of allowed connections, so the problem would not seem to be architectural in nature.

While the thousands of connections your management solution spawns will not initiate at the same time, transmission keep-alives and connection timeouts can mean that you have more connections open at any one time than you might think. Therefore you must also examine those systems that connect the rest of your network.

Let me explain. As I mentioned earlier, as network traffic passes through your network, it will pass through switches, routers, and perhaps firewalls. At any one of these points, usually the router or firewall, you may encounter intrusion detection systems. Managed switches and routers may also employ traffic filtering. You, or whoever has control over these devices, will need to check the logs for errors or warnings. The communication problem may very well lie within these systems.

Because you are connecting from an internal system to other internal systems, you may find that there are no alerts being generated, because alerting is not configured on the device or because the problem does not qualify as an intrusion or denial of service (DoS) attack. Once again, you should begin with the logs. Using ISA Server as an example, these logs can be found in the ISA Server Management console at Arrays\<ArrayName>\Monitoring\Logging.

If it is a policy that is blocking you, you may (in the case of ISA Server) look for the following result codes where the source IP is your management computer:

• 0xc0040037 FWX_E_TCP_RATE_QUOTA_EXCEEDED_DROPPED
• 0xc004000d FWX_E_POLICY_RULES_DENIED
• 0xc0040017 FWX_E_TXP_SYN_PACKET_DROPPED

If you find such results, you have identified the root of your connectivity problems.

Implementing the Solution

Now that you've identified the problem, the solution can be simple, but department politics may make it difficult to implement. Before you make any changes, make sure you have the proper permissions to do so, as creating exclusions in the security configurations on your firewalls, routers, and/or intrusion detection systems is not always allowed.

Again, using ISA Server as the example, the following steps show how to increase the maximum number of connections for a given host or for all machines in the network (as shown in Figure 4). Open ISA Server Management console and navigate to Arrays\<ArrayName>\Configuration\General\Configure Flood Mitigation Settings.

Figure 4 Increase the maximum number of connections for one host or all machines using ISA Server 

The two settings of interest are the maximum concurrent TCP connections per IP address and maximum TCP connect requests per minute per IP address. The maximum concurrent TCP connections per IP address is typically set to a value that would suffice where no active management is occurring, meaning no single computer is actively connecting to thousands of other machines quickly. In ISA Server, the default limit for maximum concurrent TCP connections is 160. The maximum TCP connect requests per minute per IP address is designed to limit the damage and visibility of network scans. The default limit is 600 connections requests per minute per IP.

As stated previously, Windows will keep a connection alive for a default period of two minutes provided nothing else is attempting to keep the connection alive, even if the connection is not in use. This means that even though you have already successfully managed a computer and no longer need to communicate with it, the connection will remain active. This open connection counts toward your total allotted connections. Repeat this process more than 160 times without removing connections and you will find that all connection attempts are being denied by your router. Even if your management program actively kills a session, Windows may well leave the connection in a time_wait state waiting for the target machine to agree to disconnect the session.

Start making adjustments to the most likely culprit: maximum concurrent TCP connections per IP address. You should set this so that your management machine will be able to create all the connections it needs to manage your systems without being denied access. Click the Edit button next to the setting and change the values.

The next prompt (see Figure 5) has a Limit box that represents the default limit, applicable to all clients. The Custom limit applies to all machines, networks, and so forth that are defined on the IP Exceptions tab of the flood mitigation dialog. If you want every machine to be permitted to create more connections, then change the value of Limit. To configure the exception for your management machine only, adjust the Custom limit and add your machine to the IP Exceptions tab. It is generally better to allow the exception for just your own machine.

Figure 5 Default connection limit and custom connection limit 

If you wish to use the custom limit to modify this value for only specific systems, then change the value in the Custom limit field and click OK. Then add your machine to the IP Exceptions tab on the flood mitigation dialog. To add your single computer to the exceptions list, on the IP Exceptions click Add to bring up the Computer Sets dialog. Click New to create a new network set to contain your system(s) if a network set containing these machines does not already exist. Select this network set and click Add to add the Internal Networks network set and click Close. Select the Internal Networks network set again and click Edit. This will open the properties for Internal Networks (see Figure 6). Click Add on this dialog to display a submenu where you can choose to add a computer, address range, or subnet; choose computer. Type in a name to identify the entry, the machine's IP address, and a description so that anyone looking at this entry later will not feel compelled to remove your system (see Figure 7). Click OK to add your system, and click it again to add the exception. Now that you have made these changes, you must apply the settings.

Figure 6 Internal networks properties settings 

Figure 7 Enter computer name, IP address, and description to ensure your system is not removed 

Try your proactive management tool again and you should find that the performance is much better and the connection does not fail—at least not as a result of network traffic. In the end, it turned out that the problem was not the number of connections the software initiated, it was the lack of proper planning for those connections that caused the disruption.

Upcoming Technologies

Previous studies on EEG-based brain-computer interaction (BCI) have typically made use of communication between a human brain and computer. In these studies, electrodes attached to a person's scalp record electrical currents in the brain as a person realises an action-thought, such as consciously thinking about moving the arm or leg. The computer then interprets that signal and translates it to a control output, such as a robot or wheelchair.

But, in this new study, the research team added a second human brain on the other end of the system. Four healthy participants, aged 28 to 50, participated in the study. One of the four subjects was assigned to the brain-computer interface (BCI) branch and was the sender of the words; the other three were assigned to the computer-brain interface (CBI) branch of the experiments and received the messages and had to understand them.

Using EEG, the research team first translated the greetings "hola" and "ciao" into binary code, then emailed the results from India to France. There a computer-brain interface transmitted the message to the receiver's brain through non-invasive brain stimulation. The subjects experienced this as phosphenes, flashes of light in their peripheral vision. The light appeared in numerical sequences that enabled the receiver to decode the information in the message, and while the subjects did not report feeling anything, they did correctly receive the greetings.

A second similar experiment was conducted between people in Spain and France, the end result being a total error rate of just 15 percent, 11 percent on the decoding end and five percent on the initial coding side.

"By using advanced precision neurotechnologies including wireless EEG and robotised TMS, we were able to directly and noninvasively transmit a thought from one person to another, without them having to speak or write," says Pascual-Leone. "This in itself is a remarkable step in human communication, but being able to do so across a distance of thousands of miles is a critically important proof-of-principle for the development of 

brain-to-brain communications. We believe these experiments represent an important first step in exploring the feasibility of complementing or bypassing traditional language-based or motor-based communication."

Upcoming Technologies