On Feb 20, 2005, at 9:00 AM, Jochem van Dieten wrote:

> Dick Applebaum wrote:
>> On Feb 20, 2005, at 7:07 AM, Jochem van Dieten wrote:
>>> Dick Applebaum wrote:
>>>>
>>>> Spotlight way
>>>>
>>>> 1) upload & save file -- automatically extracts metadata/content  
>>>> and
>>>> inserts into an sql db
>>>> 2) cfexecute CLI mdfind command to search metadata/content & return
>>>> matches
>>>
>>> How are you going to run an MacOS CLI command from a Linux CF server?
>>
>> ssh
>
> SSH through cfexecute? And I suppose you would use NFS to store
> the file on the Mac mini so it would get indexed in the first place.
>


AFAIK, you can... If the following statements are true:

As an operating system with a Unix core, Mac OS X is able to support 
the Network File System (NFS) protocol. NFS is the accepted industry 
standard for sharing files between Unix systems.

Although NFS is a built-in component of Mac OS X, users cannot access 
this feature without special knowledge and use of the command-line. NFS 
Manager solves this problem by providing an easy-to-use Aqua interface 
for the definition of NFS connections.

A Mac OS X computer can either
        �       make folders available to the network so that they can be 
shared 
with other Mac OS X or Unix computers.
        �       The system can also access files of other Mac OS X or Unix 
computers that have been made available via NFS.

I have had no need to use NFS, so I have not tried this.

Conceivably, you could expand the OS X metadata indexing/searching to 
include files resident on non-OS X boxes-- though it would not be as 
fast (for indexing).  Consider:

1) With CFMX7, you could use an Event Gateway, to watch a directory 
structure on a non-Os X box.
2) When an event is triggered, your CF/Java app could request (of the 
OS X box) indexing (importing) of the files and add it to a metadata 
store for that box (this store could be anywhere, but properly should 
reside on the same box as the indexed files).
3) Searches would be performed by the OS X box, via cfexecute 
(discussed earlier).  The search could be controlled to search across 
multiple metadata stores (boxes) or limited to a specific directory 
structure.

The Event Gateway and triggered indexing are necessary because the 
non-OS X file systems do not automatically trigger and perform 
metadata/content indexing.

It may sound a little gross, but it is prolly more efficient and 
up-to-date than Verity.

Or, just save the files on the OS X box & it is all done automatically.

BTW, there are other ways than SSH... to perform the search.  On The OS 
X box, the "searcher" runs as a OS  process, handling 0-n concurrent 
client metadata search requests. Applications like the Finder, CLI, 
Mail, iChat, iTunes, iPhoto, etc., can all perform metadata searches.  
This is roughly analogous to a db server handling simultaneous requests 
from clients on the same box (except it is done at the OS level).  I 
think that somebody, with even my limited 'Nix knowledge, could write 
an API that allows requests from other client boxes.

If I were to do this, I would make it look and act as close, as I 
could, to cfquery.... a cfmdquery custom tag.... After all, it just a 
SQLite db with a bunch of predefined table columns.

Dick

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Logware (www.logware.us): a new and convenient web-based time tracking 
application. Start tracking and documenting hours spent on a project or with a 
client with Logware today. Try it for free with a 15 day trial account.
http://www.houseoffusion.com/banners/view.cfm?bannerid=67

Message: http://www.houseoffusion.com/lists.cfm/link=i:4:195663
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54

Reply via email to