On 13-12-2011 19:21, Arno Garrels wrote:
We don't want to open and load a text file each
> time a new type is found.
True, that would be dog-slow.
For the generality of the HTTP server applications, other than the 10 or
15 most common MIME types (that should always be in the list) and the
on
Angus Robertson - Magenta Systems Ltd wrote:
>>> We don't want to open and load a text file each
>>> time a new type is found.
>> True, that would be dog-slow.
>
> We need to think about Linux/OSX, this will be first use of registry
> access in ICS, I've already done some stuff to help decoding MI
> I'm just about to change to HttpServer MIME handling again, to use a
look-up list
> read from the Windows classes registry or a text file) when the server
starts,
> to replace the current hard coded MIME list. It will be editable by the
application.
The implementation should be delegated to
> > We don't want to open and load a text file each
> > time a new type is found.
> True, that would be dog-slow.
We need to think about Linux/OSX, this will be first use of registry
access in ICS, I've already done some stuff to help decoding MIME email
content.
> > I agree that memory is neede
Angus Robertson - Magenta Systems Ltd wrote:
>> If filling from the registry, better if the list is filled
>> dynamically when a not yet resolved file extension is requested.
>
> Except that scanning a single registry node or file, allocating memory
> for those nodes, and building indexes for them
> If filling from the registry, better if the list is filled
> dynamically when a not yet resolved file extension is requested.
Except that scanning a single registry node or file, allocating memory
for those nodes, and building indexes for them may be more efficient in
one function. We don't w
RTT wrote:
> On 13-12-2011 08:31, Angus Robertson - Magenta Systems Ltd wrote:
>> I'm just about to change to HttpServer MIME handling again, to use a
>> look-up list read from the Windows classes registry or a text file)
>> when the server starts, to replace the current hard coded MIME list.
>
>
Denis Gottardello wrote:
> Il 13/12/2011 15.52, Arno Garrels ha scritto:
>> Denis Gottardello wrote:
>>> I use ICS components in a my application. I have a problem with
>>> TWSocket and ServerWSocketDataAvailable. Sometimes, when the
>>> ServerWSocketDataAvailable event is called and in action, the
Denis Gottardello wrote:
> Is possible to use TWSocket object without events contest? I want to
> use a familiar way for me. I like to create a thread for each
> connection.
Some higher level protocols provide synchronous methods, however
the base TWSocket has to be used async.
--
Arno Garrels
>>> I use ICS components in a my application. I have a problem with
>>> TWSocket and ServerWSocketDataAvailable. Sometimes, when the
>>> ServerWSocketDataAvailable event is called and in action, the same
>>> event is called again, before the previous instance is terminated.
>>>
>>> I use line mo
> Is possible to use TWSocket object without events contest?
> I want to use a familiar way for me.
> I like to create a thread for each connection.
Not sure I understand your question!
Facts:
a) you cannot use TWSocket without using events.
b) you can use TWSocket in a thread. There are samples
On 13-12-2011 14:43, Arno Garrels wrote:
I would not link headers with MIME types (in the same list) but rather
keep it clear and simple. This new class should also be usable from
other components such as the SMTP client.
Totally agree with that. Associating header elements to the content-type
i
On 13-12-2011 08:31, Angus Robertson - Magenta Systems Ltd wrote:
I'm just about to change to HttpServer MIME handling again, to use a
look-up list read from the Windows classes registry or a text file) when
the server starts, to replace the current hard coded MIME list.
If filling from the reg
Il 13/12/2011 15.52, Arno Garrels ha scritto:
Denis Gottardello wrote:
I use ICS components in a my application. I have a problem with
TWSocket and ServerWSocketDataAvailable. Sometimes, when the
ServerWSocketDataAvailable event is called and in action, the same
event is called again, before the
Is possible to use TWSocket object without events contest? I want to use
a familiar way for me. I like to create a thread for each connection.
--
Denis Gottardello
Sintesi S.r.l.
049.9301135
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org
Denis Gottardello wrote:
> I use ICS components in a my application. I have a problem with
> TWSocket and ServerWSocketDataAvailable. Sometimes, when the
> ServerWSocketDataAvailable event is called and in action, the same
> event is called again, before the previous instance is terminated.
>
> I
Angus Robertson - Magenta Systems Ltd wrote:
>> Persistant headers are not usefull cause only certain Mimetype need
>> special headers
>> And I believe this is not just a special scenario for our apps.
>> According to Pagespeed and feedback from our users this relative
>> simple change (Date and Ex
I use ICS components in a my application. I have a problem with TWSocket
and ServerWSocketDataAvailable. Sometimes, when the
ServerWSocketDataAvailable event is called and in action, the same event
is called again, before the previous instance is terminated.
I use line mode, #13#10 as line ter
> Persistant headers are not usefull cause only certain Mimetype need
> special headers
> And I believe this is not just a special scenario for our apps.
> According to Pagespeed and feedback from our users this relative
> simple change (Date and Expire headers) improved the response times
I'
19 matches
Mail list logo
