Anybody able to develop with this component locally (windows xp) in any reasonable manner? Production is Linux, but I'm wondering if the flock() limitation for NFS file systems is going to give me issues if I try to develop with it on my local server.

I will be starting this piece of my app on Monday, so I guess I'll find out the hard way....

Any insight is appreciated though....

Are you asking if it works over NFS or are you asking if it works on windows?

From the manual:
"flock() will not work on NFS and many other networked file systems.".
"Index size is limited by 2GB for 32-bit platforms."

Developing with lucene on your local machine (running xp) should be no problem as long as you're not running 32bit win and have indexes over 2gb or are using a networked FS.

Well, it is 32 bit (though I don't see the index going over 2gb during development). So that shouldn't be a problem.

However, the File System is NFS (as should be expected on WinXP), which may be a problem for Zend_Search_Lucene's use of flock...

What I'm wondering is if I develop locally, can I also test locally? And if I test locally, will flock fail gracefully or throw an error.
If I have to upload stuff to our Linux Dev server to test (which is going to kill my productivity, but oh well) I will.

This is just an educated guess, meaning I give no guarantee, but I think that you should be able to test it localy. The problem with flock over nfs is that only the process(or possibly computer) that issues the lock will know about the lock. But since you will be the only user on your local machine it doesn't matter.

If you are unlucky flock will return false when on nfs which could result in fatal errors, depending on it's usage in Lucene. But I don't think this will be a problem.

Cool. So far so good. Haven't run into any show stopping issues on NFS for my local development.

__________________
- xentek

RU sure, that you're using NFS? XPs are more likely to use NTFS (NT File System) - not NFS (Network File System).