Flex Calendar Component

This calendar component is great. It’s still has some bugs in it, but it’s my favorite Flex calendar component out there.

It was originally developed by Ely Greenfield and some bug fixes and enhancements were made by Jove Shi. This post exists because Jove’s site is offline and I’m sure people would like to benefit from his hard work, so I am hosting what I believe to be Jove’s latest source (download below). If Ely or Jove have a problem with me hosting it, please let me know and I’ll take it down.

Ely’s post about it

Ely’s Example Page:

Jove’s enhancements and bug fixes:
Download (.zip) 823KB

Maximum Concurrent HTTP Requests from Adobe AIR

The limit is 450.

Why did you test this and who cares?
I care. I was working on an application that has (potentially) hundreds of concurrent data requests and I needed to know if that was going to be a problem.

I built a Flex 3 application that had 1 HTTPService object and I called the send() method 1000 times using a for loop. I had a script that tracked the number of iterations, which reached 1000 instantly. I had a script that counted the number of responses received by the result handler. It got to 450.

My first test made requests from localhost (apache) and the responses totaled 450 within about a second. My second test made requests from another apache server about 50 miles away in a large data center; they totaled 450 within about 3 seconds. For my third test I sent 1000 requests and after about 250 were received I sent another 1000 requests. From 2000 requests, about 700 were received.

I concluded from this that there can be a total of 450 concurrent http requests pending at any given time. I tried more tests with multiple HTTPService objects and called them each 500 times. Still, the total number of received was 450. So it seems the limit is part of AIR itself and not the HTTPService object.

That made sense because when a Flex application is deployed in a browser, you’re limited by the browser’s maximum number of http connections. Typically, that number is between 2 and 50 – many modern browsers will let you adjust this number.

To adjust this number in FireFox: type “about:config” in the address bar and hit enter. Then, type “connections” in the filter box. You’ll see a number of connection settings that you can adjust. The faster your connection, the more simultaneous requests you can allow and still maintain a comfortable browsing experience.

450 connections is a lot and in most cases, far more than you need. I’m glad the AIR limit is very high; because this is one of the few ways to get information in and out of AIR. With some hard work, this is a viable way to communicate with other localhost software that may provide connections to USB or other devices – one of the current limitations of AIR.

– Chad Upton

Guided Setup, Using Perforce with Flex Builder

Perforce software makes a plug-in for Eclipse that makes life a lot easier when using the two together. This setup guide is directed specifically at using Perforce with Flex Builder 3.

As we know, Flex Builder 3 (FB3) is based on Eclipse 3.3.1. Since Flex Builder 2 is based on Eclipse 3.1.2, it probably won’t work – the release notes for the plug-in suggest is works on 3.2 and 3.3 only. I have not tested it, but if you were to upgrade Eclipse and use the Flex Builder plug-in then you should be OK.


  1. Open Flex Builder 3.
  2. Choose the following menu command: HELP > Software Updates > Find and Install.
  3. Select “Search for new features to install” and click Next >.
  4. Click “New Remote Site”.
  5. In the dialogue box, enter the Name “Perforce Plugin”.
  6. In the dialogue box, enter the URL: http://www.perforce.com/downloads/http/p4-wsad/install/
  7. Click OK.
  8. Click Finish.
  9. You will be prompted to “Select the features to install”.
  10. Be sure to check, “Show the latest version of a feature only” (at the bottom of the window)
  11. Fully expand the “Perforce Plugin” tree.
  12. Choose the last item in the tree that begins, “P4WSAD”.
  13. Click Next.
  14. Accept the terms in the license agreement to continue.
  15. Click Next.
  16. Click Finish.
  17. The feature will be downloaded and you may receive a Feature Verification warning
  18. Click “Install” if you receive the Feature Verification warning.
  19. The installation should occur and you need to restart Flex Builder.
  20. When Flex Builder restarts, we’ll tell the plugin where it can find Perforce on our system.
  21. Choose: Window > Preferences.
  22. In the left column, browse to: Team > Perforce.
  23. Under “Location of p4 executable” select “Location” and click “Browse”, then locate and select p4.exe. The default location is C:\Program Files\Perforce\p4.exe.
  24. Click Open.
  25. Click Apply.
  26. Click OK.
  27. Now, locate and open the project that you wish to use with Perforce.
  28. Right click on the project folder and choose: Team > Share Project.
  29. Select Perforce and click Next.
  30. The “Recent” field will probably be blank and that’s fine.
  31. Port will be the IP address and port of your Perforce server. (ex. If you already have P4V or P4Win setup then you can find this in the title bar of the application.
  32. User is going to be your Perforce username, likely given you to by an administrator.
  33. Client Workspace should also be found in the title bar of P4V or P4Win if you’ve got those setup.
  34. Charset can probably be left to the default (none) but may require changing in certain circumstances.
  35. Click Finish.
  36. You will likely be prompted for your Perforce password – the one that goes with the Perforce username you entered.

Assuming everything went smoothly, you should now be able to edit files and Flex Builder will automatically add that file to the default changelist and make the file writable so you don’t get that annoying message.

Some other useful things that this plug-in does. Go to Window > Other Views…
In this dialogue box you can open the Perforce folder and select “P4 Pending Changelists”. This view will show you the files you have opened for editing and allow you to right click on the changelist or individual file for submitting.

Also, you’re probably used to seeing error and warning messages in the Problems view. Now you’ll see info messages when some things are out of sync with the repository. For example, if you add a new file your project but it’s not in the repository then you’ll see an info message warning you. Right click on the file and choose “Open for Add” then Submit the changelist and it will be added.

I hope this makes your life easier and please send me a quick line if you found any errors in my instructions, that will help other people!

Further details on setup are available at the Perforce website: http://www.perforce.com/perforce/doc.073/user/p4wsadnotes.txt