On a web server, we plan to pull back a file stored in SQL in a FILESTREAM using the Win32 streaming API. Are there any special ports that must be opened to make this work? Or will the standard 1433 suffice?
From documentation:
Remote file system access to FILESTREAM data is enabled over the Server Message Block (SMB) protocol.
If you want to use the streaming API, you'll need to open SMB access to your web server from the outside: probably not a best idea if the web server is public.
Related
I am writing cmis server impl that connects to a documentum server for file upload and retrieval.
I have the Repository Class, RepositoryManager Class, Service and serviceFactory class created. I am not sure where to provide the documentum server url and root folder details in these classes and make a connection.
Should i be giving them in the repository.properties file and read them during the service initialization?
I am referring the OpenCMIS Filehsare Server Implementation code and "CMIS and Apache Chemistry in Action book".
I have connected to documentum servers through cmis client, by creating a session with the documentum url, user name and password establish a connection. But from server side, am not sure how to connect to.
Is there some specific reason why you're writing your own implementation of CMIS for Documentum? Documentum has it's own implementation, have a look at https://community.emc.com/docs/DOC-10327. I tried it and it works without a problem.
I've been studying NFS and what I don't understand is this: after the client receives the filehandle from the server (all the way at the end of the whole NFS/mountd/NFSd etc. communication process) is the file data then written somewhere on the client? And then the client reads/writes to that file on the client and then sends it back over the network to the server? Or is the client reading and writing to this file on the server over the network? Thanks!
As name says NFS (network File system) means accessing the files residing on the server. So every client NFS request either READ/WRITE will fetch the data from server over the network. Usually all NFS client implementaions will use some File caching/data caching mechanism. Once the data is read from server, it could store the data in its own cache (like buffer cache etc) for subsequent reads so as to improve the performance. As long as the client cache is valid, it doesn't need to go and fetch the data from server again and again.
I have a webpage which contains the button to upload a file. My requirement is, when user chooses the file to upload and click the submits it, the file should get transferred to an SFTP server. My question is, do I need a SSH client installed on the client machine for achieving this?
I thought of uploading it to my http server as a temp file first and then to the SFTP server from there, but then what's the purpose of SFTP on the first place as the file will be transmitted to server as unencrypted.
JSP is a server side technology. If JSP is going to be involved, then the code has to run on the server.
My question is, do I need a SSH client installed on the client machine for achieving this?
No. The server has to do the work.
I thought of uploading it to my http server as a temp file first and then to the SFTP server from there
That's how you would have to do it.
There's no way to interact with the SFTP protocols directly from client side code in a webpage.
then to the SFTP server from there, but then what's the purpose of SFTP on the first place
Good question: But you decided to use that technology, so that's up to you.
as the file will be transmitted to server as unencrypted.
To secure communications between the browser and the HTTP server, use HTTPS instead of plain HTTP.
Is there a client tool available to execute FAST queries on a remote FAST ESP 5.3 server that is accessible over http?
If the server is accessible over http, you can probably go directly to the qr (query/results) server on port 15100 of the admin node & send queries to it directly via wget. The entire query api can be used via http, results will come back in xml or plaintext depending on which search template you select (/cgi-bin/xsearch or /cgi-bin/search on generic deployments).
Details on the full query language and url params can be found here:
Fast 5.3 Query Language Parameters Guide (doc hosted on a non-Fast/MS site ... couldn't find it on msdn, but its what you want).
good luck.
I want to make an app that displays new data whenever they arrive inside a folder via xml. I want to use html5 web sockets but I am confused on how it should be done. I am using xaamp on my machine for development. Do I have to install another server to use websockets? Is apache as it is compatible and if yes how do I make the connection with the client. Thank you in advance..
Your options are:
Use something like mod_websocket, as pointed out by Phillip Kovalev. Or pywebsocket. You could also try PHP WebSocket.
Use a dedicated self-hosted realtime web technology for realtime communication between server and client. If you do this you'll also need to define a way of application to realtime web server communications - normally achieved through message queues.
Use a hosted realtime web solution and offload the realtime push aspect of your application.
There are concerns about using Apache with this type of technology since this technology maintains long-running persistent connections between the server and client and Apache isn't know to be too great at this. So, the best solution may be to:
Go with a 2nd dedicated realtime web server in conjunction with using Apache as your application server
Use a self-hosted realtime web server that has the ability to handle many concurrent connections
Use a hosted service along with your Apache application server.
If you don't expect many concurrent connections or if you are just trying out the technology then it's possible that Apache alone will be all you need.
Look at mod_websocket. It supports latest and commonly implemented by browsers vendors protocol version.