Re: BSC Mapper rewrite

[Kevin Hawkins <lists@xxxxxxxxxxxxxxxxx>]

Paul Gale wrote:
> I think it does what I want. I never put it to full use as it has to
run on my server and it brings it down if left for a number of hours :(
>
> Paul.
>
If you can ascertain it offers you what you need (without further
enhancement requests) I'll take a look at modifying it.  James' OCX
operates quite differently to Patricks', which , depending on how the
application is written can make this an easy or a difficult task. .
Perhaps run it on another PC to try for a while.  It's footprint only
grows proportional to the xAP traffic you have so removing prolific
traffic applications will allow it to run longer.

Kevin


>
>
> -----Original Message-----
> From: xap_automation@xxxxxxx [mailto:xap_automation@xxxxxxx] On
Behalf Of Kevin Hawkins
> Sent: 23 March 2006 14:28
> To: xap_automation@xxxxxxx
> Subject: Re: [xap_automation] BSC Mapper rewrite
>
> Does the HV app provide you the functionality you need as it is
> (ignoring the leak).    I may be able to look at how entwined the OCX
is
> in Ascentiums code (which I have) but I don't really want to have to
> enhance or maintain the application as I don't now have an easy way of
> testing it.
>
>      Kevin
>
> Paul Gale wrote:
>
>> I don't need the mapper but I'm desperate to get the HV app
re-written to fix the mem leak.
>>
>> Can anyone do this?
>>
>> Thanks,
>>
>> Paul.
>>
>>
>>
>> -----Original Message-----
>> From: xap_automation@xxxxxxx [mailto:xap_automation@xxxxxxx] On
Behalf Of Kevin Hawkins
>> Sent: 23 March 2006 01:11
>> To: xap_automation@xxxxxxx
>> Subject: [xap_automation] BSC Mapper rewrite
>>
>> I am in the process of re-writing BSC Mapper (originally by
Ascentium)
>> to use James' OCX rather than Patricks and hence fix the memory
leak. If
>> anyone has any other wishlist items with regard to this
application
>> please shout now...
>>
>>  Kevin
>>
>>
>>
>>
>>
>>
>
>
>
>