[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference ucrow::desktop_acms

Title:	DECtp Desktop for ACMS

Moderator:	UCROW::GIBSON

Created:	Mon Sep 24 1990
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	859
Total number of notes:	3034

838.0. "MacTCP tool limitation?" by STKAI1::PEGERT () Fri Apr 04 1997 05:25

    Hi,
    
    My name is Ann Pegert working with a customer using ACMS Desktop for
    Macintosh! They have used DECnet as a communication tool for many
    years, but are now forced to use TCP/IP instead.
    They have done some tests and everything works fine with one exception
    - large workspaces or rather the sum of workspaces exceeding 32K in one
    single call makes the application hang! (The connection string is set
    up correctly specifying buffersize 32764!)
    
    Can someone confirm that this is due to a limitation in the MacTCP tool
    and nothing else? I need something good to hand over to the customer,
    who of course is very reluctant to modify the defined workspaces if not
    absolutely necessary!
    
    Do you know of any plans to rewrite the MacTCP tool?
    Could ACMSDI be modified to handle this?
    
    Is there a recommendation in the release notes about not using
    workspaces that add up to more than 32K for V2.2 of ACMSDI? (I can look
    it up myself when I go to the customer site!)
    
    Will there also be a V2.3 of ACMSDI for the Macintosh? What new
    features can one expect?
    
    Any information that can soothe the customer is gratefully received.
    
    Thanks,
    Ann

T.R	Title	User	Date	Lines
838.1	Not allowing for control data?	EYEORE::BAIRD	`Fri Apr 04 1997 13:01`	22
	Hi Ann, I just ran a test using the MacTCP Tool and was able to sent a 32764 buffer. Maybe the problem is that the customer isn't allowing for the control data in the buffer. If their total size of all workspaces is 32764 they have to allow for a buffer size of (say) 32800 to accomodate the control data that gets packed into the message along with the workspaces themselves. The symptom of the application just hanging fits this scenario. HOWEVER, there's a catch. 32764 is the largest buffer size allowable, and that's not just for the MacTCP Tool. The difference is that other tools don't require that the whole message fit into one buffer as the MacTCP Tool does. So I guess the only solution is to reduce the total buffer size to 32764 by reducing some of the workspace sizes. There is another problem with the server side which the customer may encounter. (The problem you're describing is not it.) The problem I'm referring to is the ACMSDI$SERVER process access violating under certain conditions when passing large workspaces. I can't remember the exact details and your customer may not encounter it but, if this happens, we have an ECO that can be applied to fix it.
838.2	Answers to your questions	EYEORE::BAIRD	`Fri Apr 04 1997 13:17`	31
	Hi again, To answer your questions: >> Do you know of any plans to rewrite the MacTCP tool? The MacTCP Tool is not part of the ACMS Desktop product. Any rewrite would have to come from Apple Computer or the PATHWORKS folks. >> Could ACMSDI be modified to handle this? It may be possible to modify ACMSDI to handle more than 32764 buffer sizes. I say "may be" but I'm not sure of this. There may be a technical problem that I'm not aware of. But there has to be some limit in any case. If we bumped it up to (say) 35000, sooner or later someone would come along looking for 35001. So the question is where do we set the limit? >> Is there a recommendation in the release notes about not using >> workspaces that add up to more than 32K for V2.2 of ACMSDI? (I can >> look it up myself when I go to the customer site!) I can't remember. >> Will there also be a V2.3 of ACMSDI for the Macintosh? What new >> features can one expect? There will be no changes to the Mac platform for V2.3. The problem is that there are very few Mac customers and that number is deminishing. We have to concentrate our resources where the most customers needs will be addressed.
838.3	Conclusion	STKAI1::PEGERT	`Mon Apr 07 1997 05:01`	13
	Hallo again, Yes, I am aware that MacTCP comes from Apple, but I was hoping that this iisue had been addressed by some other ACMSDI Mac users and that some contact had been established with Apple..... Thats' why I asked! It seems there is only one solution then - modify the workspaces (and the application)! Thanks for your help! Regards, Ann