Date: 2005-02-22 10:07:17 +0100
From: @sjoerdmullender
To: GDK devs <>
Version: -- development

Last updated: 2019-04-30 12:36:05 +0200

Comment 13405

Date: 2005-02-22 10:07:17 +0100
From: @sjoerdmullender

It might be nice to have the ability to open and read
remote files through the HTTP protocol. We should take
a look at curl to see if that can be integrated into
stream.mx.

The reason for wanting to do this is so that we can
make demos easily usable without having to distribute
them with the binaries.

Comment 13406

Date: 2005-02-22 10:38:20 +0100
From: @grobian

Logged In: YES
user_id=963970

shouldn't this functionality be just in the client, instead
of the server?

Comment 13407

Date: 2005-02-22 10:48:26 +0100
From: @mlkersten

Logged In: YES
user_id=490798

Yes. This functionality is needed at several levels.

1. mm objects should be represented in the DBMS with a
   handle and could be represented by urls to their origin. A
   function getContent(() could then read the information into
   a string/BAT/.... for further processing in the context of
   the session.
   (Additional functions could forward it to a browser)

2. the functionality of MonetDB would greatly improve if it
   would be
   possible to access read-only bats using a URL. Actually, the
   access could also trigger a coercion to internal format. For
   example, accessing a remote jpg file using the http protocol
   delivers a BAT with the color representations (combined with
   getWidth() and getHeight() on this file type you have an
   image at your disposal.

Comment 13408

Date: 2005-02-22 10:59:21 +0100
From: @grobian

Logged In: YES
user_id=963970

I don't see why for internal operations the stream library
would be used.

For demos, the customer just wants to execute a remote file:
a zip, a tar, a tar/gzip, a gzip, a plain text file. You
can do that by defining (non standard) handles within the
language you are demoing in, or just by keeping it simple
and letting the client fetch and feed to the Mserver.

For a demo, everything is already there, in fact it's just a
matter of "MapiClient | curl" or wget, or links, or lynx, etc.

Comment 13409

Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <>

This bug was previously known as tracker item 1146064 at http://sourceforge.net/support/tracker.php?aid=1146064

Comment 26814

Date: 2019-01-21 14:45:08 +0100
From: @sjoerdmullender

In the next feature release there will be support for COPY INTO table FROM 'some:/url' ON CLIENT, if mclient is started with the --allow-remote option.